Re: [fmc] fmc Digest, Vol 9, Issue 9
Hasnaa Moustafa <hasnaa.moustafa@gmail.com> Fri, 14 December 2012 17:51 UTC
Return-Path: <hasnaa.moustafa@gmail.com>
X-Original-To: fmc@ietfa.amsl.com
Delivered-To: fmc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B9CE21F8A91 for <fmc@ietfa.amsl.com>; Fri, 14 Dec 2012 09:51:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.902
X-Spam-Level: **
X-Spam-Status: No, score=2.902 tagged_above=-999 required=5 tests=[AWL=-6.200, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_26=0.6, J_CHICKENPOX_35=0.6, MANGLED_DELETE=2.3, MANGLED_FORM=2.3, MANGLED_MEDS=2.3, MANGLED_PLEASE=2.3, MANGLED_TEXT=2.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bCk-7-OC3+st for <fmc@ietfa.amsl.com>; Fri, 14 Dec 2012 09:51:36 -0800 (PST)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7500F21F8A8E for <fmc@ietf.org>; Fri, 14 Dec 2012 09:51:35 -0800 (PST)
Received: by mail-vc0-f172.google.com with SMTP id fw7so4413375vcb.31 for <fmc@ietf.org>; Fri, 14 Dec 2012 09:51:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ic/YoTK00ZdPLX/NG+rCF2OQw1EOWd9rw6SXJZd+8ws=; b=bOmNOST2sM3aZQXmQRba73vgFAx98AR53kzSusFoaZBoGooRbkx6e0g87ggecYWD1y 2kGsy2IFWjw4JoBLwFq+LShp2PcX23JmaTxPIBGrs+SbkXtd1Mdu5erZoSThMZmQ4lz2 id62GxH7IzsmoNBFr6b/8lR1pQjLSMRvFOG7/tKOW9L8UDETJYP0JHNgHkzxbyFwqwlq HB67rhZYI2ASgefKyfzbpBRyRkfmF64RKyiIuOB8A3vJgbDvIjKT6B5Lsm0RZCTO5+2B /5em0JU0RJDOJ21Txtd3d0z8W/QyTkUmI79qOVptKOzMQK5SpSCYkyKD/bYp3kpnAvH4 EUlQ==
MIME-Version: 1.0
Received: by 10.52.155.205 with SMTP id vy13mr6517992vdb.119.1355507494828; Fri, 14 Dec 2012 09:51:34 -0800 (PST)
Received: by 10.58.252.37 with HTTP; Fri, 14 Dec 2012 09:51:34 -0800 (PST)
In-Reply-To: <mailman.3911.1355467316.3374.fmc@ietf.org>
References: <mailman.3911.1355467316.3374.fmc@ietf.org>
Date: Fri, 14 Dec 2012 09:51:34 -0800
Message-ID: <CAO0u4SEB_5eSZpSfY-mGozSfuFPhn4oE=tzQsu_4Ws97C4tzVA@mail.gmail.com>
From: Hasnaa Moustafa <hasnaa.moustafa@gmail.com>
To: fmc@ietf.org
Content-Type: multipart/alternative; boundary="bcaec53aecceb83a2104d0d3ae05"
Cc: mohamed.boucadair@orange.com
Subject: Re: [fmc] fmc Digest, Vol 9, Issue 9
X-BeenThere: fmc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Fixed Mobile Convergence <fmc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/fmc>, <mailto:fmc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/fmc>
List-Post: <mailto:fmc@ietf.org>
List-Help: <mailto:fmc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/fmc>, <mailto:fmc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Dec 2012 17:51:50 -0000
Dear Med, Thanks for the clarification. Yes I agree with your feedback on the video streaming case. Your reply makes things clearer for me, yes this is more situated under "a solution approacg" and I think that it's nearly covered by the different use'cases mentioned in the draft. For the SIPTO case, I understood that you confirm the interest of including a use-case for it. And so I will provide you shortly with some text proposal seeing if it meets the scope for Host-ID use-cases. Kind regards, Hassnaa On Thu, Dec 13, 2012 at 10:41 PM, <fmc-request@ietf.org> wrote: > If you have received this digest without all the individual message > attachments you will need to update your digest options in your list > subscription. To do so, go to > > https://www.ietf.org/mailman/listinfo/fmc > > Click the 'Unsubscribe or edit options' button, log in, and set "Get > MIME or Plain Text Digests?" to MIME. You can set this option > globally for all the list digests you receive at this point. > > > > Send fmc mailing list submissions to > fmc@ietf.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://www.ietf.org/mailman/listinfo/fmc > or, via email, send a message with subject or body 'help' to > fmc-request@ietf.org > > You can reach the person managing the list at > fmc-owner@ietf.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of fmc digest..." > > Today's Topics: > > 1. Re: fmc Digest, Vol 9, Issue 7 (mohamed.boucadair@orange.com) > 2. (no subject) > > > ---------- Forwarded message ---------- > From: <mohamed.boucadair@orange.com> > To: Hasnaa Moustafa <hasnaa.moustafa@gmail.com>, "fmc@ietf.org" < > fmc@ietf.org> > Cc: > Date: Fri, 14 Dec 2012 07:41:49 +0100 > Subject: Re: [fmc] fmc Digest, Vol 9, Issue 7 > ** > Dear Hasnaa, > > Please see inline. > > Cheers, > Med > > ------------------------------ > *De :* Hasnaa Moustafa [mailto:hasnaa.moustafa@gmail.com] > *Envoyé :* jeudi 13 décembre 2012 19:38 > *À :* fmc@ietf.org > *Cc :* BOUCADAIR Mohamed OLNC/OLN > *Objet :* Re: fmc Digest, Vol 9, Issue 7 > > Thanks Med for your clarification. > For yur first question ([Med] Wouldn't this be achieved at the > application level? announce/discover the device capabilities and then the > server will adapt the way it will server the device?) ---> YES sure this > is taken care by the application level (as HAS and DASH cases), but the > question is: Would doing so by lower layers through the host-ID be > beneficial and provide a generic standardized solution to any application > on top? would there be a agin? would this way of doing it help? > Here, I really have a question rather than a proposal for this I thought > sharing this point with you and with the mailing list (since the Host-ID > issue in the way you describe could help "this is what I thought at least - > but with no strong sureness"). > [Med] The current use cases described in the draft present host > identification as a problem. The content adaptation case you are describing > is looking on how to make use of any HOST_ID proposal to better service the > device/user. This is another perspective. I prefer to restrict the scope of > the draft to only cases where host identification is an issue. > > For the second point on the SIPTO, I understood that it fits under the > Cellular Network use-case in the draft (with no need to include a new > use-case for Heterogeneous networks/Small cells)? > [Med] SIPTO can be introduced as a new use case in its own. > > A last question (which was asked before I think in one of the previous > emails commenting the draft): Would the Host-ID issue mentioned in the > draft be a discussion base for FMC (or would be under one of the existing > WGs)? > [Med] The goal is to assess whether there is interest from the community > to solve this problem. The problem space is not restricted to FMC but > covers various cases which share the same technical problem. Today this > document is still "homeless"... > > Thanks for this exchange. > > Kind regards, > Hassnaa > > On Wed, Dec 12, 2012 at 11:01 PM, <fmc-request@ietf.org> wrote: > >> If you have received this digest without all the individual message >> attachments you will need to update your digest options in your list >> subscription. To do so, go to >> >> https://www.ietf.org/mailman/listinfo/fmc >> >> Click the 'Unsubscribe or edit options' button, log in, and set "Get >> MIME or Plain Text Digests?" to MIME. You can set this option >> globally for all the list digests you receive at this point. >> >> >> >> Send fmc mailing list submissions to >> fmc@ietf.org >> >> To subscribe or unsubscribe via the World Wide Web, visit >> https://www.ietf.org/mailman/listinfo/fmc >> or, via email, send a message with subject or body 'help' to >> fmc-request@ietf.org >> >> You can reach the person managing the list at >> fmc-owner@ietf.org >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of fmc digest..." >> >> Today's Topics: >> >> 1. Re: fmc Digest, Vol 9, Issue 3 (mohamed.boucadair@orange.com) >> >> >> ---------- Forwarded message ---------- >> From: <mohamed.boucadair@orange.com> >> To: Hasnaa Moustafa <hasnaa.moustafa@gmail.com>, "fmc@ietf.org" < >> fmc@ietf.org> >> Cc: "draft-boucadair-intarea-host-identifier-scenarios@tools.ietf.org" < >> draft-boucadair-intarea-host-identifier-scenarios@tools.ietf.org> >> Date: Thu, 13 Dec 2012 08:01:21 +0100 >> Subject: Re: [fmc] fmc Digest, Vol 9, Issue 3 >> ** >> Dear Hasnaa, >> >> Thank you for reading the draft. >> >> Please see inline. >> Cheers, >> Med >> >> ------------------------------ >> *De :* fmc-bounces@ietf.org [mailto:fmc-bounces@ietf.org] *De la part de*Hasnaa Moustafa >> *Envoyé :* mardi 11 décembre 2012 20:22 >> *À :* fmc@ietf.org >> *Objet :* Re: [fmc] fmc Digest, Vol 9, Issue 3 >> >> >> >> Dear Med, >> >> >> >> I read the draft and have some issues to discuss on the use-cases. >> >> I think that Host-ID would be useful for the case of Home Networks in a >> scenario as follows: >> >> - Several hosts exist in the home network that can belong to the same >> or multiple users >> >> - The NAT functionality could be carried out either in the RG or in >> another Border node >> >> - The host access could be through WiFi AP, FAP or even Ethernet (e.g. >> connected TV) >> >> - Video streaming is the popular application/traffic in home network >> through the different hosts >> >> - Each host is considered as a device with different characteristics >> (i.e. requiring the end server to distinguish each device to provide >> the adequate content for each host) for better QoE >> >> - Each host has a private IPv4 address while there is one shared public >> IPv4 address by all the Home Network >> >> - Consequently, a HostID solution is beneficial in this use case >> >> >> >> I am not sure if the motivation for Host-ID need in such scenario matches >> the objective of Host-ID in your draft and if this scenario is implicitly >> covered in some of the use-cases mentioned in the draft. >> >> [Med] Wouldn't this be achieved at the application >> level? announce/discover the device capabilities and then the server will >> adapt the way it will server the device? >> >> >> >> Another case that could be checked maybe is the HetNets scenario. >> According to 3GPP definition for HetNets/small cells: Small cells are lower >> power nodes working in the same frequency as the macro cell nodes, and the >> heterogeneity of the network comes from the varying power levels within the >> deployed nodes. >> >> A host could be attached to one or more small cells and could be >> simultaneously attached to a small cell and a macro cell at the same time. >> Private IPv4 addresses are assigned in each cell (macro or pico), and there >> could be several scenarios as follows: >> >> - host attached to only the macro cell: similar HostID issue to >> the cellular network use-case >> >> - host attached to only a small cell: similar HostID issue to >> the case of cellular network use-case >> >> - host attached to both the macro cell and a small cell: >> Selected IP Traffic Offload is enabled by NAT based on operator policies >> (e.g. per IP address) [3GPP TR 23.829]. Here there might be a new issue ? >> >> [Med] Thank you for sharing this use case. >> >> > > ---------- Forwarded message ---------- > From: > To: > Cc: > Date: > Subject: > er=20 > not only for the small cell case but in for mobile networks in > genera= > l.=20 > The SIPTO case may induce some issues for both IPv4 and IPv6.=20 > </FONT></SPAN></P> > <P style=3D"LINE-HEIGHT: normal; MARGIN: 0in 0in 0pt"=20 > class=3DMsoNormal><SPAN><FONT color=3D#0000ff=20 > face=3D"Courier New"></FONT></SPAN> </P> > <P style=3D"LINE-HEIGHT: normal; MARGIN: 0in 0in 0pt"=20 > class=3DMsoNormal><SPAN><FONT color=3D#0000ff=20 > face=3D"Courier New"></FONT></SPAN> </P> > <P style=3D"LINE-HEIGHT: normal; MARGIN: 0in 0in 0pt"=20 > class=3DMsoNormal><SPAN> </SPAN>I thought to share thes epoints > = > with=20 > you and with all the list for more feedback.<BR><SPAN><FONT > color=3D#= > 0000ff=20 > face=3D"Courier New">[Med] Many thanks for sharing your=20 > thoughts. I will be more than please to integrate you text on > th= > e=20 > SIPTO case. </FONT></SPAN></P></SPAN><SPAN=20 > style=3D"FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt"></SPAN> > <P style=3D"LINE-HEIGHT: normal; MARGIN: 0in 0in 0pt" > class=3DMsoNorm= > al><SPAN=20 > style=3D"FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: > 10pt"></SPAN>&= > nbsp;</P> > <P style=3D"LINE-HEIGHT: normal; MARGIN: 0in 0in 0pt" > class=3DMsoNorm= > al><SPAN=20 > style=3D"FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt">Kind=20 > regards,</SPAN><SPAN=20 > style=3D"FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: > 10pt"></SPAN><= > /P> > <P style=3D"LINE-HEIGHT: normal; MARGIN: 0in 0in 6pt" > class=3DMsoNorm= > al><SPAN=20 > style=3D"FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: > 10pt">Hassnaa<= > /SPAN><SPAN=20 > style=3D"FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: > 10pt"></SPAN><= > /P> </DIV> > <DIV><BR><BR> </DIV> > <DIV class=3Dgmail_quote>On Fri, Dec 7, 2012 at 7:17 AM, Hassnaa > Mous= > tafa=20 > <SPAN dir=3Dltr><<A href=3D"mailto:hasnaa.moustafa@gmail.com"=20 > target=3D_blank>hasnaa.moustafa@gmail.com</A>></SPAN> wrote:<BR> > <BLOCKQUOTE=20 > style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; > PADD= > ING-LEFT: 1ex"=20 > class=3Dgmail_quote> > <DIV style=3D"WORD-WRAP: break-word"><BR> > <DIV><BR> > <DIV>Begin forwarded message:</DIV><BR> > <BLOCKQUOTE type=3D"cite"> > <DIV style=3D"MARGIN: 0px"><SPAN=20 > style=3D"FONT-FAMILY: 'Helvetica'; FONT-SIZE: medium"><B>From:=20 > </B></SPAN><SPAN=20 > style=3D"FONT-FAMILY: 'Helvetica'; FONT-SIZE: medium"><A=20 > href=3D"mailto:fmc-request@ietf.org"=20 > target=3D_blank>fmc-request@ietf.org</A><BR></SPAN></DIV> > <DIV style=3D"MARGIN: 0px"><SPAN=20 > style=3D"FONT-FAMILY: 'Helvetica'; FONT-SIZE: > medium"><B>Subject:= > =20 > </B></SPAN><SPAN=20 > style=3D"FONT-FAMILY: 'Helvetica'; FONT-SIZE: medium"><B>fmc > Dige= > st, Vol=20 > 9, Issue 3</B><BR></SPAN></DIV> > <DIV style=3D"MARGIN: 0px"><SPAN=20 > style=3D"FONT-FAMILY: 'Helvetica'; FONT-SIZE: medium"><B>Date:=20 > </B></SPAN><SPAN=20 > style=3D"FONT-FAMILY: 'Helvetica'; FONT-SIZE: medium">December > 7,= > 2012=20 > 12:27:41 AM PST<BR></SPAN></DIV> > <DIV style=3D"MARGIN: 0px"><SPAN=20 > style=3D"FONT-FAMILY: 'Helvetica'; FONT-SIZE: medium"><B>To:=20 > </B></SPAN><SPAN=20 > style=3D"FONT-FAMILY: 'Helvetica'; FONT-SIZE: medium"><A=20 > href=3D"mailto:fmc@ietf.org"=20 > target=3D_blank>fmc@ietf.org</A><BR></SPAN></DIV> > <DIV style=3D"MARGIN: 0px"><SPAN=20 > style=3D"FONT-FAMILY: 'Helvetica'; FONT-SIZE: > medium"><B>Reply-To= > :=20 > </B></SPAN><SPAN=20 > style=3D"FONT-FAMILY: 'Helvetica'; FONT-SIZE: medium"><A=20 > href=3D"mailto:fmc@ietf.org"=20 > target=3D_blank>fmc@ietf.org</A><BR></SPAN></DIV> > <DIV> > <DIV><BR>If you have received this digest without all the > individ= > ual=20 > message<BR>attachments you will need to update your digest > option= > s in=20 > your list<BR>subscription. To do so, go to <BR><BR><A=20 > href=3D"https://www.ietf.org/mailman/listinfo/fmc"=20 > target=3D_blank>https://www.ietf.org/mailman/listinfo/fmc > </A><BR>= > <BR>Click=20 > the 'Unsubscribe or edit options' button, log in, and set > "Get<BR= > >MIME=20 > or Plain Text Digests?" to MIME. You can set this=20 > option<BR>globally for all the list digests you receive at > this=20 > point.<BR><BR><BR><BR>Send fmc mailing list submissions > to<BR><SP= > AN=20 > style=3D"WHITE-SPACE: pre-wrap"></SPAN><A href=3D"mailto: > fmc@ietf= > .org"=20 > target=3D_blank>fmc@ietf.org</A><BR><BR>To subscribe or > unsubscri= > be via=20 > the World Wide Web, visit<BR><SPAN=20 > style=3D"WHITE-SPACE: pre-wrap"></SPAN><A=20 > href=3D"https://www.ietf.org/mailman/listinfo/fmc"=20 > target=3D_blank>https://www.ietf.org/mailman/listinfo/fmc > </A><BR>= > or, via=20 > email, send a message with subject or body 'help' to<BR><SPAN=20 > style=3D"WHITE-SPACE: pre-wrap"></SPAN><A=20 > href=3D"mailto:fmc-request@ietf.org"=20 > target=3D_blank>fmc-request@ietf.org</A><BR><BR>You can reach > the= > person=20 > managing the list at<BR><SPAN style=3D"WHITE-SPACE: > pre-wrap"></S= > PAN><A=20 > href=3D"mailto:fmc-owner@ietf.org"=20 > target=3D_blank>fmc-owner@ietf.org</A><BR><BR>When replying, > plea= > se edit=20 > your Subject line so it is more specific<BR>than "Re: Contents > of= > fmc=20 > digest..."<BR></DIV></DIV>Today's Topics:<BR><BR> 1. > R= > e:=20 > > [Int-area]<BR> draft-boucadair-intar= > ea-host-identifier-scenarios=20 > (Tina TSOU)<BR><BR> > <DIV style=3D"MARGIN: 0px"><SPAN=20 > style=3D"FONT-FAMILY: 'Helvetica'; FONT-SIZE: medium"><B>From:=20 > </B></SPAN><SPAN=20 > style=3D"FONT-FAMILY: 'Helvetica'; FONT-SIZE: medium">Tina TSOU > &= > lt;<A=20 > href=3D"mailto:Tina.Tsou.Zouting@huawei.com"=20 > target=3D_blank>Tina.Tsou.Zouting@huawei.com > </A>><BR></SPAN></= > DIV> > <DIV style=3D"MARGIN: 0px"><SPAN=20 > style=3D"FONT-FAMILY: 'Helvetica'; FONT-SIZE: > medium"><B>Subject:= > =20 > </B></SPAN><SPAN=20 > style=3D"FONT-FAMILY: 'Helvetica'; FONT-SIZE: medium"><B>Re: > [fmc= > ]=20 > [Int-area]=20 > > draft-boucadair-intarea-host-identifier-scenarios</B><BR></SPAN><= > /DIV> > <DIV style=3D"MARGIN: 0px"><SPAN=20 > style=3D"FONT-FAMILY: 'Helvetica'; FONT-SIZE: medium"><B>Date:=20 > </B></SPAN><SPAN=20 > style=3D"FONT-FAMILY: 'Helvetica'; FONT-SIZE: medium">December > 6,= > 2012=20 > 11:16:00 PM PST<BR></SPAN></DIV> > <DIV style=3D"MARGIN: 0px"><SPAN=20 > style=3D"FONT-FAMILY: 'Helvetica'; FONT-SIZE: medium"><B>To:=20 > </B></SPAN><SPAN=20 > style=3D"FONT-FAMILY: 'Helvetica'; FONT-SIZE: medium">"<A=20 > href=3D"mailto:mohamed.boucadair@orange.com"=20 > target=3D_blank>mohamed.boucadair@orange.com</A>" <<A=20 > href=3D"mailto:mohamed.boucadair@orange.com"=20 > target=3D_blank>mohamed.boucadair@orange.com > </A>><BR></SPAN></= > DIV> > <DIV style=3D"MARGIN: 0px"><SPAN=20 > style=3D"FONT-FAMILY: 'Helvetica'; FONT-SIZE: medium"><B>Cc:=20 > </B></SPAN><SPAN=20 > style=3D"FONT-FAMILY: 'Helvetica'; FONT-SIZE: medium">"<A=20 > href=3D"mailto: > draft-boucadair-intarea-host-identifier-scenarios@= > tools.ietf.org"=20 > > target=3D_blank>draft-boucadair-intarea-host-identifier-scenarios= > @tools.ietf.org</A>"=20 > <<A=20 > href=3D"mailto: > draft-boucadair-intarea-host-identifier-scenarios@= > tools.ietf.org"=20 > > target=3D_blank>draft-boucadair-intarea-host-identifier-scenarios= > @tools.ietf.org</A>>,=20 > "<A href=3D"mailto:int-area@ietf.org"=20 > target=3D_blank>int-area@ietf.org</A>" <<A=20 > href=3D"mailto:int-area@ietf.org"=20 > target=3D_blank>int-area@ietf.org</A>>, "<A=20 > href=3D"mailto:fmc@ietf.org" target=3D_blank>fmc@ietf.org</A>" > &l= > t;<A=20 > href=3D"mailto:fmc@ietf.org" target=3D_blank>fmc@ietf.org > </A>>= > ,=20 > "George, Wes" <<A href=3D"mailto:wesley.george@twcable.com > "=20 > target=3D_blank>wesley.george@twcable.com > </A>><BR></SPAN></DIV= > ><BR><BR> > <DIV bgcolor=3D"#FFFFFF"> > <DIV><SPAN>Dear Med et al,</SPAN></DIV> > <DIV> > <DIV style=3D"MARGIN: 0cm 0cm 0pt"><SPAN lang=3DEN-US>In > general,= > I like=20 > the current version. Some comments are=20 > below.<U></U><U></U></SPAN></DIV> > <DIV style=3D"TEXT-INDENT: 0px; MARGIN: 0cm 0cm 0pt > 18pt"><SPAN=20 > lang=3DEN-US><SPAN>1.<SPAN=20 > style=3D"FONT: 7pt 'Times New > Roman'"> &nb= > sp; </SPAN></SPAN></SPAN><SPAN=20 > lang=3DEN-US>From my understanding, this document provides the > us= > e cases=20 > for the issues and analysis in=20 > =93draft-ietf-intarea-nat-reveal-analysis=94. Is it correct? If > i= > t is , I=20 > suggest this document be referenced in=20 > =93nat-reveal-analysis=94.<U></U><U></U></SPAN></DIV> > <DIV style=3D"TEXT-INDENT: 0px; MARGIN: 0cm 0cm 0pt > 18pt"><SPAN=20 > lang=3DEN-US><SPAN>2.<SPAN=20 > style=3D"FONT: 7pt 'Times New > Roman'"> &nb= > sp; </SPAN></SPAN></SPAN><SPAN=20 > lang=3DEN-US>Regarding this document, in the section of CGN use > c= > ase,=20 > the stateless NAT44 case should be=20 > included.<U></U><U></U></SPAN></DIV> > <DIV style=3D"TEXT-INDENT: 0px; MARGIN: 0cm 0cm 0pt > 18pt"><SPAN=20 > lang=3DEN-US><SPAN>3.<SPAN=20 > style=3D"FONT: 7pt 'Times New > Roman'"> &nb= > sp; </SPAN></SPAN></SPAN><SPAN=20 > lang=3DEN-US>For A+P section, the MAP/Lw4over6 cases may be=20 > considered.<U></U><U></U></SPAN></DIV> > <DIV style=3D"TEXT-INDENT: 0px; MARGIN: 0cm 0cm 0pt > 18pt"><SPAN=20 > lang=3DEN-US><SPAN>4.<SPAN=20 > style=3D"FONT: 7pt 'Times New > Roman'"> &nb= > sp; </SPAN></SPAN></SPAN><SPAN=20 > lang=3DEN-US>In figure 6, the UE may have an interface with AF > to= > =20 > initiate the session request, e.g., SIP.</SPAN></DIV> > <DIV><BR></DIV> > <DIV>Thank you,</DIV>Tina</DIV> > <DIV><BR>On Dec 4, 2012, at 11:10 PM, "<A=20 > href=3D"mailto:mohamed.boucadair@orange.com"=20 > target=3D_blank>mohamed.boucadair@orange.com</A>" <<A=20 > href=3D"mailto:mohamed.boucadair@orange.com"=20 > target=3D_blank>mohamed.boucadair@orange.com</A>>=20 > wrote:<BR><BR></DIV> > <DIV></DIV> > <BLOCKQUOTE type=3D"cite"> > <DIV><SPAN>Dear Wes,</SPAN><BR><SPAN></SPAN><BR><SPAN>Thank > you= > for=20 > your comments. </SPAN><BR><SPAN></SPAN><BR><SPAN>Please see > inl= > ine.=20 > > </SPAN><BR><SPAN></SPAN><BR><SPAN>Cheers,</SPAN><BR><SPAN>Med=20 > </SPAN><BR><SPAN></SPAN><BR> > <BLOCKQUOTE type=3D"cite"><SPAN>-----Message=20 > d'origine-----</SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN>De : George, Wes [mailto:<A=20 > href=3D"mailto:wesley.george@twcable.com"=20 > target=3D_blank>wesley.george@twcable.com</A>]=20 > </SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN>Envoy=E9 : mardi 4 d=E9cembre > 2= > 012=20 > 21:09</SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN>=C0 : BOUCADAIR Mohamed > OLNC/OL= > N; <A=20 > href=3D"mailto:fmc@ietf.org" target=3D_blank>fmc@ietf.org > </A>= > ; <A=20 > href=3D"mailto:int-area@ietf.org"=20 > target=3D_blank>int-area@ietf.org > </A></SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN>Cc : <A=20 > href=3D"mailto: > draft-boucadair-intarea-host-identifier-scenar= > ios@tools.ietf.org"=20 > > target=3D_blank>draft-boucadair-intarea-host-identifier-scena= > rios@tools.ietf.org</A></SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN>Objet : RE:=20 > > draft-boucadair-intarea-host-identifier-scenarios</SPAN><BR><= > /BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN></SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN>I've read this draft, and I > thi= > nk=20 > the use case list is </SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN>reasonably=20 > complete.</SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN></SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN>However, it's really unclear > to= > me=20 > what the value of this </SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN>draft might be in its current > f= > orm,=20 > and what its intended </SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN>audience might be. Cataloging > u= > se=20 > cases is not all that </SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN>helpful by itself without an > en= > d=20 > goal in mind, and that end </SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN>goal is not clear from the=20 > draft.</SPAN><BR></BLOCKQUOTE><SPAN></SPAN><BR><SPAN>Med: > The= > goal=20 > of this draft is what is described in Section=20 > 2:</SPAN><BR><SPAN></SPAN><BR><SPAN>"The goal is=20 > to</SPAN><BR><SPAN> identify scenarios the authors > a= > re=20 > aware of and which share the > same</SPAN><BR><SPAN> i= > ssue=20 > of host=20 > > identification.</SPAN><BR><SPAN></SPAN><BR><SPAN> Th= > is=20 > document does not include any solution-specific=20 > discussion.</SPAN><BR><SPAN> This document can be > us= > ed as=20 > a tool to design solution(s)=20 > mitigating</SPAN><BR><SPAN> the encountered issues.= > =20 > Having a generic solution which would=20 > solve</SPAN><BR><SPAN> the issues encountered in > the= > se=20 > use cases is preferred over > designing</SPAN><BR><SPAN> &nb= > sp;a=20 > solution for each use case. Describing the use case > allow= > s=20 > to</SPAN><BR><SPAN> identify what is common between > = > the=20 > use cases and then would > help</SPAN><BR><SPAN> durin= > g the=20 > solution design > phase."</SPAN><BR><SPAN></SPAN><BR><SPAN>Next=20 > updates of this draft will:</SPAN><BR><SPAN>* include a > discuss= > ion=20 > section to assess whether the issue is valid for IPv4-only or > i= > t=20 > applies also for IPv6</SPAN><BR><SPAN>* include a discussion > te= > xt to=20 > clarify whether each use case is valid within one single=20 > administrative domain or not</SPAN><BR><SPAN>* include a > discus= > sion=20 > text to identify use cases which share the same requirements > (t= > his=20 > will help in designing the solution) </SPAN><BR><SPAN>* add=20 > additional use cases if > any</SPAN><BR><SPAN></SPAN><BR><SPAN>At= > =20 > given point in time we need to draw conclusions about the=20 > following:</SPAN><BR><SPAN>(1) are these use cases valid=20 > ones?</SPAN><BR><SPAN>(2) if this is a real technical problem, > = > what=20 > the IETF can do to solve the issue?</SPAN><BR><SPAN>(3) if > ther= > e is=20 > interest in this area, how to organize the work for the > solutio= > n=20 > space.</SPAN><BR><SPAN></SPAN><BR><SPAN>The scope is > deliberate= > ly=20 > </SPAN><BR> > <BLOCKQUOTE type=3D"cite"><SPAN>very narrow and references > othe= > r=20 > drafts that discuss some of </SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN>the surrounding issues with > add= > ress=20 > sharing and unique </SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN>identifiers, and so there is > ve= > ry=20 > little text in each section </SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN>beyond a basic description. > Eve= > n=20 > when you think of this in </SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN>terms of follow-on drafts such > = > as a=20 > gap analysis or problem </SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN>statement or solution drafts, > o= > ne=20 > wonders how useful it is to </SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN>spread this across multiple > dra= > fts.=20 > So why not simply </SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN>incorporate this list into one > = > of=20 > the referenced general </SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN>drafts on host identification, > = > such=20 > as nat-reveal-analysis and </SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN>then broaden that draft so > that= > it=20 > considers and addresses the </SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN>other use cases as=20 > > appropriate?</SPAN><BR></BLOCKQUOTE><SPAN></SPAN><BR><SPAN>Me= > d: As I=20 > mentioned above, we don't want to include any > solution-specific= > =20 > discussion to this draft. The text is shortened in=20 > purpose.</SPAN><BR><SPAN></SPAN><BR> > <BLOCKQUOTE type=3D"cite"><SPAN></SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN>Otherwise, I think that the > dra= > ft=20 > needs to be much clearer </SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN>about the unique issues and=20 > considerations for each use case, </SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN>especially those that are > someh= > ow=20 > distinct from those covered </SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN>in nat-reveal-analysis so that > = > it=20 > can serve as a better input </SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN>to any potential solutions=20 > addressing this=20 > problem.</SPAN><BR></BLOCKQUOTE><SPAN></SPAN><BR><SPAN>Med: > Ful= > ly=20 > agreed. This will be added to the next rev of the=20 > draft.</SPAN><BR><SPAN></SPAN><BR> > <BLOCKQUOTE type=3D"cite"><SPAN></SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN>I also believe that if this > dra= > ft is=20 > to remain a standalone </SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN>document, the authors need to > m= > ake=20 > at least some attempt at </SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN>discussing security and > privacy= > =20 > considerations here, even if </SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN>it is mainly to refer the > reade= > r to=20 > more in-depth discussions </SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN>of the matter in other=20 > drafts.</SPAN><BR></BLOCKQUOTE><SPAN></SPAN><BR><SPAN>Med: > Ag= > ree. A=20 > pointer to <A=20 > href=3D" > http://tools.ietf.org/html/draft-ietf-intarea-nat-revea= > l-analysis-04#section-3"=20 > target=3D_blank> > http://tools.ietf.org/html/draft-ietf-intarea-n= > at-reveal-analysis-04#section-3</A>=20 > will be added to the next rev of the draft. The text will also= > =20 > include some discussion for use cases which are restricted to > o= > ne=20 > single administrative=20 > > domain.</SPAN><BR><SPAN></SPAN><BR><SPAN></SPAN><BR><SPAN>Again= > ,=20 > here is an area where </SPAN><BR> > <BLOCKQUOTE type=3D"cite"><SPAN>being clear about the specific= > =20 > considerations for each use </SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN>case is important, identifying= > =20 > whether the other drafts </SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN>discuss things so that they > are= > =20 > applicable to all of the use </SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN>cases, or if the use cases are= > =20 > unique in any number of ways </SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN>that will mean that they have > u= > nique=20 > privacy and security </SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE=20 > type=3D"cite"><SPAN>considerations.</SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN></SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN>Thanks,</SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN></SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN>Wes > George</SPAN><BR></BLOCKQUO= > TE> > <BLOCKQUOTE type=3D"cite"><SPAN></SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE type=3D"cite"><SPAN>-----Original=20 > Message-----</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE type=3D"cite"><SPAN>From: <A=20 > href=3D"mailto:int-area-bounces@ietf.org"=20 > target=3D_blank>int-area-bounces@ietf.org</A> [mailto: > <A=20 > href=3D"mailto:int-area-bounces@ietf.org"=20 > target=3D_blank>int-area-bounces@ietf.org</A>]=20 > On</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE type=3D"cite"><SPAN>Behalf Of <A=20 > href=3D"mailto:mohamed.boucadair@orange.com"=20 > target=3D_blank>mohamed.boucadair@orange.com > </A></SPAN><BR>= > </BLOCKQUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE type=3D"cite"><SPAN>Sent: Monday, December 03, > 20= > 12=20 > 4:08 AM</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE type=3D"cite"><SPAN>To: <A href=3D"mailto: > fmc@iet= > f.org"=20 > target=3D_blank>fmc@ietf.org</A>; <A=20 > href=3D"mailto:int-area@ietf.org"=20 > target=3D_blank>int-area@ietf.org > </A></SPAN><BR></BLOCKQUOT= > E></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE type=3D"cite"><SPAN>Cc: <A=20 > href=3D"mailto: > draft-boucadair-intarea-host-identifier-scen= > arios@tools.ietf.org"=20 > > target=3D_blank>draft-boucadair-intarea-host-identifier-sce= > narios@tools.ietf.org</A></SPAN><BR></BLOCKQUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE type=3D"cite"><SPAN>Subject: [Int-area]=20 > > draft-boucadair-intarea-host-identifier-scenarios</SPAN><BR= > ></BLOCKQUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE > type=3D"cite"><SPAN></SPAN><BR></BLOCKQUOTE></BLO= > CKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE type=3D"cite"><SPAN>Dear=20 > all,</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE > type=3D"cite"><SPAN></SPAN><BR></BLOCKQUOTE></BLO= > CKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE type=3D"cite"><SPAN>We submitted an updated > versi= > on of=20 > this draft to list use cases=20 > which</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE type=3D"cite"><SPAN>encounter the issue of > host=20 > identification. The following > </SPAN><BR></BLOCKQUOTE></BLO= > CKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN>use cases > are</SPAN><BR></BLOCK= > QUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE type=3D"cite"><SPAN>discussed in the=20 > draft:</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE > type=3D"cite"><SPAN></SPAN><BR></BLOCKQUOTE></BLO= > CKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE type=3D"cite"><SPAN> (1) > Carrier= > =20 > Grade NAT (CGN)</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE type=3D"cite"><SPAN> (2) A+P > (e.= > g.,=20 > MAP )</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE type=3D"cite"><SPAN> (3) > Applica= > tion=20 > Proxies</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE type=3D"cite"><SPAN> (4) > Provide= > r=20 > Wi-Fi</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE type=3D"cite"><SPAN> (5) Policy > = > and=20 > Charging Architectures</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE type=3D"cite"><SPAN> (6) > Cellula= > r=20 > Networks</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE type=3D"cite"><SPAN> (7)=20 > Femtocells</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE type=3D"cite"><SPAN> (8) > Overlay= > =20 > Networks (e.g., CDNs)</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE > type=3D"cite"><SPAN></SPAN><BR></BLOCKQUOTE></BLO= > CKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE type=3D"cite"><SPAN>The document does not > include= > any=20 > solution-specific </SPAN><BR></BLOCKQUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN>discussion. Its=20 > main</SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE type=3D"cite"><SPAN>goal is to identify the use > c= > ases=20 > and describe them.</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE > type=3D"cite"><SPAN></SPAN><BR></BLOCKQUOTE></BLO= > CKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE type=3D"cite"><SPAN>If you think your use case > is= > not=20 > included in this version, > </SPAN><BR></BLOCKQUOTE></BLOCKQU= > OTE> > <BLOCKQUOTE type=3D"cite"><SPAN>please > share</SPAN><BR></BLOCKQ= > UOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE type=3D"cite"><SPAN>it with=20 > us.</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE > type=3D"cite"><SPAN></SPAN><BR></BLOCKQUOTE></BLO= > CKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE type=3D"cite"><SPAN>Comments are=20 > welcome.</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE > type=3D"cite"><SPAN></SPAN><BR></BLOCKQUOTE></BLO= > CKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE=20 > > type=3D"cite"><SPAN>Cheers,</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE= > > > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE=20 > type=3D"cite"><SPAN>Med</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE > type=3D"cite"><SPAN></SPAN><BR></BLOCKQUOTE></BLO= > CKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE > type=3D"cite"><SPAN></SPAN><BR></BLOCKQUOTE></BLO= > CKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE type=3D"cite"><SPAN>-----Message=20 > d'origine-----</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE type=3D"cite"><SPAN>De : <A=20 > href=3D"mailto:i-d-announce-bounces@ietf.org"=20 > target=3D_blank>i-d-announce-bounces@ietf.org</A> [mailto: > <= > A=20 > href=3D"mailto:i-d-announce-"=20 > > target=3D_blank>i-d-announce-</A></SPAN><BR></BLOCKQUOTE></= > BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE type=3D"cite"><SPAN><A href=3D"mailto: > bounces@iet= > f.org"=20 > target=3D_blank>bounces@ietf.org</A>] De la part de <A=20 > href=3D"mailto:internet-drafts@ietf.org"=20 > target=3D_blank>internet-drafts@ietf.org</A>=20 > </SPAN><BR></BLOCKQUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN>Envoy=E9 : > lundi</SPAN><BR></BL= > OCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE type=3D"cite"><SPAN>3 d=E9cembre 2012 08:26 =C0 > := > <A=20 > href=3D"mailto:i-d-announce@ietf.org"=20 > target=3D_blank>i-d-announce@ietf.org</A> Objet : I-D=20 > Action:</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE=20 > > type=3D"cite"><SPAN>draft-boucadair-intarea-host-identifier= > -scenarios-02.txt</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE > type=3D"cite"><SPAN></SPAN><BR></BLOCKQUOTE></BLO= > CKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE > type=3D"cite"><SPAN></SPAN><BR></BLOCKQUOTE></BLO= > CKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE type=3D"cite"><SPAN>A New Internet-Draft is > avail= > able=20 > from the on-line=20 > Internet-Drafts</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE=20 > > type=3D"cite"><SPAN>directories.</SPAN><BR></BLOCKQUOTE></BLOCK= > QUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE > type=3D"cite"><SPAN></SPAN><BR></BLOCKQUOTE></BLO= > CKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE > type=3D"cite"><SPAN></SPAN><BR></BLOCKQUOTE></BLO= > CKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE=20 > type=3D"cite"><SPAN> Title=20 > >  = > ;:=20 > Host Identification: Use > Cases</SPAN><BR></BLOCKQUOTE></BLO= > CKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE=20 > > type=3D"cite"><SPAN> Author(s)= > =20 > : Mohamed=20 > Boucadair</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE=20 > > type=3D"cite"><SPAN> &nb= > > sp; = > David=20 > Binet</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE=20 > > type=3D"cite"><SPAN> &nb= > > sp; = > Sophie=20 > Durel</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE=20 > > type=3D"cite"><SPAN> &nb= > > sp; = > Tirumaleswar=20 > Reddy</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE=20 > > type=3D"cite"><SPAN> &nb= > > sp; = > Brandon=20 > Williams</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE=20 > type=3D"cite"><SPAN> Filename= > =20 > :=20 > > draft-boucadair-intarea-host-identifier-</SPAN><BR></BLOCKQ= > UOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE=20 > > type=3D"cite"><SPAN>scenarios-02.txt</SPAN><BR></BLOCKQUOTE><= > /BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE=20 > type=3D"cite"><SPAN> Pages=20 > >  = > ;:=20 > 14</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE > type=3D"cite"><SPAN>  = > ;Date=20 > >  = > ; :=20 > 2012-12-02</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE > type=3D"cite"><SPAN></SPAN><BR></BLOCKQUOTE></BLO= > CKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE=20 > > type=3D"cite"><SPAN>Abstract:</SPAN><BR></BLOCKQUOTE></BLOCKQUO= > TE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE type=3D"cite"><SPAN> This document=20 > describes a set of scenarios in which=20 > host</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE type=3D"cite"><SPAN> identification > is= > =20 > required.</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE > type=3D"cite"><SPAN></SPAN><BR></BLOCKQUOTE></BLO= > CKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE > type=3D"cite"><SPAN></SPAN><BR></BLOCKQUOTE></BLO= > CKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE type=3D"cite"><SPAN>The IETF datatracker status > p= > age=20 > for this draft is:</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE type=3D"cite"><SPAN><A=20 > href=3D" > https://datatracker.ietf.org/doc/draft-boucadair-in= > tarea-host-"=20 > target=3D_blank> > https://datatracker.ietf.org/doc/draft-bouc= > adair-intarea-host-</A></SPAN><BR></BLOCKQUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE=20 > > type=3D"cite"><SPAN>identifier-scenarios</SPAN><BR></BLOCKQUO= > TE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE > type=3D"cite"><SPAN></SPAN><BR></BLOCKQUOTE></BLO= > CKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE type=3D"cite"><SPAN>There's also a htmlized > versi= > on=20 > available at:</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE type=3D"cite"><SPAN><A=20 > href=3D" > http://tools.ietf.org/html/draft-boucadair-intarea-= > host-identifier-"=20 > target=3D_blank> > http://tools.ietf.org/html/draft-boucadair-= > intarea-host-identifier-</A></SPAN><BR></BLOCKQUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE=20 > > type=3D"cite"><SPAN>scenarios-02</SPAN><BR></BLOCKQUOTE></BLOCK= > QUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE > type=3D"cite"><SPAN></SPAN><BR></BLOCKQUOTE></BLO= > CKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE type=3D"cite"><SPAN>A diff from the previous > vers= > ion=20 > is available at:</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE type=3D"cite"><SPAN><A=20 > href=3D" > http://www.ietf.org/rfcdiff?url2=3Ddraft-boucadair-= > intarea-host-"=20 > target=3D_blank> > http://www.ietf.org/rfcdiff?url2=3Ddraft-bo= > ucadair-intarea-host-</A></SPAN><BR></BLOCKQUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE=20 > > type=3D"cite"><SPAN>identifier-scenarios-02</SPAN><BR></BLOCK= > QUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE > type=3D"cite"><SPAN></SPAN><BR></BLOCKQUOTE></BLO= > CKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE > type=3D"cite"><SPAN></SPAN><BR></BLOCKQUOTE></BLO= > CKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE type=3D"cite"><SPAN>Internet-Drafts are also > avai= > lable=20 > by anonymous FTP at:</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE type=3D"cite"><SPAN><A=20 > href=3D"ftp://ftp.ietf.org/internet-drafts/"=20 > target=3D_blank>ftp://ftp.ietf.org/internet-drafts/ > </A></SP= > AN><BR></BLOCKQUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE > type=3D"cite"><SPAN></SPAN><BR></BLOCKQUOTE></BLO= > CKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE=20 > > type=3D"cite"><SPAN>_______________________________________= > ________</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE type=3D"cite"><SPAN>I-D-Announce mailing=20 > list</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE type=3D"cite"><SPAN><A=20 > href=3D"mailto:I-D-Announce@ietf.org"=20 > target=3D_blank>I-D-Announce@ietf.org > </A></SPAN><BR></BLOCK= > QUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE type=3D"cite"><SPAN><A=20 > href=3D"https://www.ietf.org/mailman/listinfo/i-d-announce > "= > =20 > target=3D_blank> > https://www.ietf.org/mailman/listinfo/i-d-a= > nnounce</A></SPAN><BR></BLOCKQUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE type=3D"cite"><SPAN>Internet-Draft directories: > <= > A=20 > href=3D"http://www.ietf.org/shadow.html"=20 > target=3D_blank>http://www.ietf.org/shadow.html</A>=20 > or</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE type=3D"cite"><SPAN><A=20 > href=3D"ftp://ftp.ietf.org/ietf/1shadow-sites.txt"=20 > target=3D_blank>ftp://ftp.ietf.org/ietf/1shadow-sites.txt > </= > A></SPAN><BR></BLOCKQUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE=20 > > type=3D"cite"><SPAN>_______________________________________= > ________</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE type=3D"cite"><SPAN>Int-area mailing=20 > list</SPAN><BR></BLOCKQUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE type=3D"cite"><SPAN><A href=3D"mailto: > Int-area@ie= > tf.org"=20 > target=3D_blank>Int-area@ietf.org > </A></SPAN><BR></BLOCKQUOT= > E></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"> > <BLOCKQUOTE type=3D"cite"><SPAN><A=20 > href=3D"https://www.ietf.org/mailman/listinfo/int-area"=20 > target=3D_blank> > https://www.ietf.org/mailman/listinfo/int-a= > rea</A></SPAN><BR></BLOCKQUOTE></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN></SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN>This E-mail and any of its=20 > attachments may contain Time Warner </SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN>Cable proprietary information, > = > which=20 > is privileged, </SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN>confidential, or subject to=20 > copyright belonging to Time Warner </SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN>Cable. This E-mail is intended= > =20 > solely for the use of the </SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN>individual or entity to which > i= > t is=20 > addressed. If you are not </SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN>the intended recipient of this= > =20 > E-mail, you are hereby notified </SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN>that any dissemination,=20 > distribution, copying, or action taken > </SPAN><BR></BLOCKQUOT= > E> > <BLOCKQUOTE type=3D"cite"><SPAN>in relation to the contents of > = > and=20 > attachments to this E-mail </SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN>is strictly prohibited and may > = > be=20 > unlawful. If you have </SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN>received this E-mail in error,= > =20 > please notify the sender </SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN>immediately and permanently > del= > ete=20 > the original and any copy </SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE type=3D"cite"><SPAN>of this E-mail and any=20 > printout.</SPAN><BR></BLOCKQUOTE> > <BLOCKQUOTE=20 > > type=3D"cite"><SPAN></SPAN><BR></BLOCKQUOTE><SPAN>_____________= > __________________________________</SPAN><BR><SPAN>Int-area=20 > mailing list</SPAN><BR><SPAN><A href=3D"mailto: > Int-area@ietf.or= > g"=20 > target=3D_blank>Int-area@ietf.org</A></SPAN><BR><SPAN><A=20 > href=3D"https://www.ietf.org/mailman/listinfo/int-area"=20 > target=3D_blank>https://www.ietf.org/mailman/listinfo/int-area > <= > > /A></SPAN><BR></DIV></BLOCKQUOTE></DIV><BR><BR>____________________________= > ___________________<BR>fmc=20 > mailing list<BR><A href=3D"mailto:fmc@ietf.org"=20 > target=3D_blank>fmc@ietf.org</A><BR><A=20 > href=3D"https://www.ietf.org/mailman/listinfo/fmc"=20 > target=3D_blank>https://www.ietf.org/mailman/listinfo/fmc > </A><BR>= > > </BLOCKQUOTE></DIV><BR></DIV></BLOCKQUOTE></DIV><BR></BLOCKQUOTE></DIV><BR>= > _______________________________________________<BR>fmc=20 > mailing list<BR><A href=3D"mailto:fmc@ietf.org">fmc@ietf.org > </A><BR><A= > =20 > href=3D"https://www.ietf.org/mailman/listinfo/fmc"=20 > target=3D_blank>https://www.ietf.org/mailman/listinfo/fmc > </A><BR><BR></= > BLOCKQUOTE></DIV><BR></BLOCKQUOTE></BODY></HTML> > > --_000_94C682931C08B048B7A8645303FDC9F36E9D16DF7CPUEXCB1Bnante_-- > > > ... > > [Message clipped]
- Re: [fmc] fmc Digest, Vol 9, Issue 9 Hasnaa Moustafa