Hi spencer, It sounds good to me. Thanks
Regards, Julien > -----Message d'origine----- > De : Spencer Dawkins [mailto:[email protected]] > Envoyé : lundi 17 août 2009 14:05 > À : BOURNELLE Julien RD-CORE-ISS; [email protected] > Cc : [email protected]; [email protected] > Objet : Re: Gen-ART Review of draft-ietf-dime-pmip6-02.txt > > Hi, Julian, > > If this is a concern, I would be FINE with text that says > > "Whenever the MAG sends a Diameter request message to the > HAAA, the User-Name SHOULD contain the MN's identity unless > the identity is being suppressed for policy reasons - for > example, when identity hiding is in effect." > > Does that help? > > Thanks, > > Spencer > > ----- Original Message ----- > From: <[email protected]> > To: <[email protected]>; <[email protected]> > Cc: <[email protected]>; <[email protected]> > Sent: Monday, August 17, 2009 7:57 AM > Subject: RE: Gen-ART Review of draft-ietf-dime-pmip6-02.txt > > > Hello, > > thanks for your Gen-ART review... one comment below: > > > -----Message d'origine----- > > De : Spencer Dawkins [mailto:[email protected]] > > Envoyé : lundi 10 août 2009 00:31 > > À : jouni korhonen > > Cc : [email protected]; General Area Review Team > > Objet : Re: Gen-ART Review of draft-ietf-dime-pmip6-02.txt > > > > i think we're down to one item... > > > > >>>> 5.1. MAG-to-HAAA Interface > > >>>> > > >>>> Whenever the MAG sends a Diameter request message to the > > HAAA the > > >>>> User-Name AVP SHOULD contain the MN's identity. The MN > > identity, > > >>>> if > > >>>> > > >>>> Spencer (minor): what is this SHOULD conditional on? > > >>> > > >>> In case of identity hiding is applied, the User-Name can > > be absent. > > >> > > >> Ah - if my understanding is correct, the text might be clearer as > > >> "Whenever the MAG sends a Diameter request message to > the HAAA and > > >> identity hiding is not in effect, the User-Name MUST contain the > > >> MN's identity". > > > > > > I am still a bit hesitant with the MUST here. Anyway, if > > other authors > > > don't disagree I am ok with the proposed change. > > > > I would be OK with a SHOULD - you've provided at least one > > reason why it's not an unconditional MUST - but please check > > with other authors and doc shepherd. > > > I'm ok with the proposed text. I just hope there's no other > case where the > User-Name may not be available. > > Regards, > > Julien > > > > > thanks for the quick responses! > > > > spencer > > > > >>>> available, MUST be in Network Access Identifier (NAI) [RFC4282] > > >>>> format. At minimum the home realm of the MN MUST be > > available at > > >>>> the MAG when the network access authentication takes place. > > >>>> Otherwise the MAG is not able to route the Diameter request > > >>>> messages towards the correct HAAA. The MN identity used on the > > >>>> MAG-to-HAAA interface and in the User-Name AVP MAY entirely be > > >>>> related to the network access authentication, and therefore not > > >>>> suitable to be used as the MN-ID mobility option value in the > > >>>> subsequent PBU/PBA messages. See the related > discussion on MN's > > >>>> identities in Section 4.6 and in Section 5.2.1 > > > > > > _______________________________________________ Gen-art mailing list [email protected] https://www.ietf.org/mailman/listinfo/gen-art
