Hi Tina, Thank you for the clarification. I updated the draft with a pointer to SLNAT44.
I prefer to not modify fig.6 (keep it simple + we are not dealing with signalling flows issued from the UE). Thanks for the review. Cheers, Med ________________________________ De : Tina TSOU [mailto:[email protected]] Envoyé : lundi 10 décembre 2012 20:04 À : BOUCADAIR Mohamed OLNC/OLN Cc : George, Wes; [email protected]; [email protected]; [email protected] Objet : Re: [Int-area] draft-boucadair-intarea-host-identifier-scenarios Dear Med et al, In line... Thank you, Tina On Dec 9, 2012, at 10:57 PM, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> wrote: Hi Tina, Many thanks for the comments. Please see inline. Cheers, Med ________________________________ De : Tina TSOU [mailto:[email protected]] Envoyé : vendredi 7 décembre 2012 08:16 À : BOUCADAIR Mohamed OLNC/OLN Cc : George, Wes; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> Objet : Re: [Int-area] draft-boucadair-intarea-host-identifier-scenarios Dear Med et al, In general, I like the current version. Some comments are below. 1. From my understanding, this document provides the use cases for the issues and analysis in "draft-ietf-intarea-nat-reveal-analysis". Is it correct? If it is , I suggest this document be referenced in "nat-reveal-analysis". [Med] nat-reveal-analysis draft inherits its scope from RFC6269. The use cases draft adopts a more generic scope in which host identification issue is encountered (this can be caused by address sharing, tunnelling, involvement of multiple administrative entities, etc.). 2. Regarding this document, in the section of CGN use case, the stateless NAT44 case should be included. [Med] Do you mean 1:1 NAT? [Tina] I meant the case in this document: http://datatracker.ietf.org/doc/draft-tsou-stateless-nat44/, did not mean to just promote my own draft though. 3. For A+P section, the MAP/Lw4over6 cases may be considered. [Med] OK. I will add a pointer to MAP and Lw4over6 as examples. 4. In figure 6, the UE may have an interface with AF to initiate the session request, e.g., SIP. [Med] What does that mean? The goal of fig.6 is to illustrate the case where there is a host identification issue. [Tina] In section 7, it says "The main issue is: PCEF, PCRF and AF all receive information bound to the same UE but without being able to correlate between the piece of data visible for each entity." In PCRF architecture, the AF receives service request from the UE for service establishment, which is one of the ways for AF to receive UE information, e.g., user ID. To make the architecture more generic, there should be an interface between AF and UE.
_______________________________________________ Int-area mailing list [email protected] https://www.ietf.org/mailman/listinfo/int-area
