Re: [radext] Call for WG Adoption for draft-dekok-radext-nai-02; The Network Access Identifier

Are you suggesting this due to people who are using the NAI in protocols
other than RADIUS/Diameter?  

If you don't believe that there are a large number of people doing so, then
I don't see the point of the split.

Jim

> -----Original Message-----
> From: radext-bounces@ietf.org [mailto:radext-bounces@ietf.org] On Behalf
> Of Alan DeKok
> Sent: Saturday, December 15, 2012 9:17 AM
> To: Jouni Korhonen
> Cc: Benoit Claise; radext@ietf.org; radext-chairs@tools.ietf.org
> Subject: Re: [radext] Call for WG Adoption for draft-dekok-radext-nai-02;
> The Network Access Identifier
> 
> Jouni Korhonen wrote:
> > Folks,
> >
> > As discussed in Atlanta, we are ready to ask for the WG adoption of
draft-
> dekok-radext-nai-02 (The Network Access Identifier "bis") starting today.
> The plan is that once we have had the adoption call finished we can move
the
> document straight into WGLC (knowing there are already reviews done).
> >
> > The WG adoption call ends 20th Dec. This is a quick one week call since
we
> have had the document around quite long already. If you have concerns
> against the document, raise them in the mailing list. Silence will be
counted
> as acceptance. Of course folks are encouraged to endorse the document in
> the mailing list.
> 
>   As discusses early, the document should be split in two.
> 
>   My $0.02 is to accept the document as-is, rename it to
draft-ietf-radext-
> naibis-00.txt, and then split it.
> 
>   All of the RADIUS / Diameter text will then be removed, and placed into
a
> second document: draft-iet-radext-naiusage-00.txt
> 
>   The goal is to get the NAI-bis document published quickly.  Then,
discuss the
> usage of NAI within RADIUS as a slightly longer-term project.
> 
>   Alan DeKok.
> _______________________________________________
> radext mailing list
> radext@ietf.org
> https://www.ietf.org/mailman/listinfo/radext