Re: [Dime] New draft for Diameter ERP: poll for adoption

[Sebastien Decugis <sdecugis at nict.go.jp>]

Hi,

(BTW, I propose the follow-ups directed to the DIME mailing-list only,
to avoid the cross-posting. If people from HOKEY ML are interested and
not subscribed to DIME ML, let me know...)

> AFAIK, this is not how things are working at IETF. The WG has already
> a WG document called draft-ietf-dime-erp-00.txt which is supposed to
> reflect the current WG consensus. We can't arrive with a new
> individual submission and just bypass the current WG I-D. At least, I
> never saw that.
Well, once again, sorry for the quiproquo here... I was not
ill-intended, just interested in pushing a new different direction for
the design of Diameter ERP, and submit the new idea to the WG(s) for
consideration (and eventually integration, not by-passing). Enough with
the politics on the WG lists (but I can continue in private if people
want to argue), and let's focus on technical matters...

> Having said that, we have an issue with the current WG document
> concerning use of a new Application-ID or reuse of the Diameter EAP.
> My understanding was that we were a little blocked because of an
> architectural issue concerning the HOKEY server in regards to AAA/EAP
> server and because of a routing issue. So I'd like to know what has
> changed from this point.
For the routing issue: this new proposal aims to solve it.
For the architectural issue: I think it was a misunderstanding from the
beginning, or at least I did not understand the issue, so if someone can
clarify (what the issue was), it would be helpful.

>  Note that I'm not against your proposal per se. We just have to get a
> consensus.
Of course!

Best regards,
Sebastien.

-- 
Sebastien Decugis
Research fellow
Network Architecture Group
NICT (nict.go.jp)