Re: [mif] IRON as a multiple interface solution
"Hui Deng" <denghui@chinamobile.com> Wed, 21 December 2011 10:17 UTC
Return-Path: <denghui@chinamobile.com>
X-Original-To: mif@ietfa.amsl.com
Delivered-To: mif@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 103A121F846A for <mif@ietfa.amsl.com>; Wed, 21 Dec 2011 02:17:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.377
X-Spam-Level:
X-Spam-Status: No, score=-0.377 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RELAY_IS_221=2.222]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gvloqljo+JRM for <mif@ietfa.amsl.com>; Wed, 21 Dec 2011 02:17:07 -0800 (PST)
Received: from imss.chinamobile.com (imss.chinamobile.com [221.130.253.135]) by ietfa.amsl.com (Postfix) with ESMTP id D9F2F21F8418 for <mif@ietf.org>; Wed, 21 Dec 2011 02:17:06 -0800 (PST)
Received: from imss.chinamobile.com (localhost [127.0.0.1]) by localhost.chinamobile.com (Postfix) with ESMTP id 6D671E463; Wed, 21 Dec 2011 18:17:05 +0800 (CST)
Received: from mail.chinamobile.com (unknown [10.1.28.22]) by imss.chinamobile.com (Postfix) with ESMTP id 61B90E3BC; Wed, 21 Dec 2011 18:17:05 +0800 (CST)
Received: from Hui ([10.2.53.94]) by mail.chinamobile.com (Lotus Domino Release 6.5.6) with ESMTP id 2011122118170292-18781 ; Wed, 21 Dec 2011 18:17:02 +0800
From: Hui Deng <denghui@chinamobile.com>
To: "'Templin, Fred L'" <Fred.L.Templin@boeing.com>, 'Andrew Sullivan' <ajs@anvilwalrusden.com>
References: <4EC5B720.8020605@gmail.com> <83A7D27A-9036-4252-AC94-3A89125C961B@nominum.com> <4EC63ECC.8010700@gmail.com> <E1829B60731D1740BB7A0626B4FAF0A65C7911E89A@XCH-NW-01V.nw.nos.boeing.com> <D24D78CD-CDB8-4DDE-9D08-CE747443440B@nominum.com> <E1829B60731D1740BB7A0626B4FAF0A65C7911E911@XCH-NW-01V.nw.nos.boeing.com> <20111119220355.GA893@shinkuro.com> <E1829B60731D1740BB7A0626B4FAF0A65C7911EA73@XCH-NW-01V.nw.nos.boeing.com> <CANF0JMB3--o0z7VKD_MvxYZ7APDhNjdWnGr=41NYjYh=x66pRA@mail.gmail.com> <E1829B60731D1740BB7A0626B4FAF0A65C7917B0D5@XCH-NW-01V.nw.nos.boeing.com> <20111128181115.GC45293@shinkuro.com> <E1829B60731D1740BB7A0626B4FAF0A65C791E7E06@XCH-NW-01V.nw.nos.boeing.com> <01da01ccb0d2$72f6f630$58e4e290$@com> <E1829B60731D1740BB7A0626B4FAF0A65C791E8043@XCH-NW-01V.nw.nos.boeing.com> <01ee01ccbb24$48fb0950$daf11bf0$@com> <E1829B60731D1740BB7A0626B4FAF0A65C792A5382@XCH-NW-01V.nw.nos.boeing.com> <008b01ccbedf$c5cb9620$5162c260$@com> <E1829B60731D1740BB7A0626B4FAF0A65C792A575F @XCH-NW-01V.nw.nos.boe ing.com>
In-Reply-To: <E1829B60731D1740BB7A0626B4FAF0A65C792A575F@XCH-NW-01V.nw.nos.boeing.com>
Date: Wed, 21 Dec 2011 18:17:06 +0800
Message-ID: <00a001ccbfc9$b119ede0$134dc9a0$@com>
MIME-Version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acyt+SVzR1PpkUYRTvCp3A+bmVJOzQCYBPHAAB446gAAD8Pa0AKEviEwANQukcAAGomgYAAaRdXgACBYkTA=
X-MIMETrack: Itemize by SMTP Server on jtgsml01/servers/cmcc(Release 6.5.6|March 06, 2007) at 2011-12-21 18:17:02, Serialize by Router on jtgsml01/servers/cmcc(Release 6.5.6|March 06, 2007) at 2011-12-21 18:17:04, Serialize complete at 2011-12-21 18:17:04
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
Content-Language: zh-cn
X-TM-AS-Product-Ver: IMSS-7.0.0.8231-6.8.0.1017-18596.006
X-TM-AS-Result: No--33.740-7.0-31-10
X-imss-scan-details: No--33.740-7.0-31-10;No--33.740-7.0-31-10
X-TM-AS-User-Approved-Sender: No;No
X-TM-AS-User-Blocked-Sender: No
Cc: mif@ietf.org
Subject: Re: [mif] IRON as a multiple interface solution
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multiple Interface Discussion List <mif.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mif>, <mailto:mif-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mif>
List-Post: <mailto:mif@ietf.org>
List-Help: <mailto:mif-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mif>, <mailto:mif-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Dec 2011 10:17:08 -0000
Hi Fred Current MIF is discussing 3GPP and BBF scenarios and problems, If IRON is a new architecture, then it need to clarify which scenario and PS that IRON is targeting at. Thanks -Hui > -----Original Message----- > From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com] > Sent: Wednesday, December 21, 2011 3:10 AM > To: Hui Deng; 'Andrew Sullivan' > Cc: mif@ietf.org > Subject: RE: [mif] IRON as a multiple interface solution > > Hi Hui, > > > -----Original Message----- > > From: Hui Deng [mailto:denghui@chinamobile.com] > > Sent: Monday, December 19, 2011 10:23 PM > > To: Templin, Fred L; 'Andrew Sullivan' > > Cc: mif@ietf.org > > Subject: RE: [mif] IRON as a multiple interface solution > > > > Hi Fred > > > > There are multiple places discussing virtual interface(PMIP6, > > DSMIP6, 3GPP > > GTP, Connection Manager et al.), > > Yes, virtual interfaces have been discussed in many contexts > for many, many years. But, the virtual interface described in > IRON is uniquely different. > > The virtual interface described in IRON is an NBMA interface > that views other IRON nodes as on-link neighbors. Neighbor > coordinations such as neighbor/router discovery, NUD, > redirection, etc. are therefore supported. > > IRON also uniquely solves the well known virtual interface > path MTU problem, and this is especially important for MIF > nodes that connect to diverse L2 media. > > I have also already mentioned the ability to have a > persistent L3 configuration on the IRON virtual interface > even if the L3 configurations on the ISP interfaces change > dynamically. This provides significant benefits for mobility, > mobile networks, session survivability, etc. The document > also mentions several other compelling functions applicable > to MIF nodes that are enabled. > > > > I don't know whether IETF is interested in documenting such > > implementation, > > Internet Area maybe the right place to discuss it. > > IRON is not an implementation; it is an architecture. > Its functional components are VET, SEAL and AERO, which > deal with specific aspects of concern to the MIF problem > space. The four documents (IRON, VET, SEAL and AERO) go > together as a group. > > Thanks - Fred > fred.l.templin@boeing.com > > > Thanks > > > > -Hui > > > -----Original Message----- > > > From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com] > > > Sent: Tuesday, December 20, 2011 1:44 AM > > > To: Hui Deng; 'Andrew Sullivan' > > > Cc: mif@ietf.org > > > Subject: RE: [mif] IRON as a multiple interface solution > > > > > > Hi Hui, > > > > > > > -----Original Message----- > > > > From: Hui Deng [mailto:denghui@chinamobile.com] > > > > Sent: Thursday, December 15, 2011 4:23 AM > > > > To: Templin, Fred L; 'Andrew Sullivan' > > > > Cc: mif@ietf.org > > > > Subject: RE: [mif] IRON as a multiple interface solution > > > > > > > > Hi Fred, > > > > > > > > This new interface type is also a kind of virtual interface > > > > which has been > > > > mentioned in RFC 6418. > > > > > > Yes, I see where virtual interfaces are mentioned in > > > several places in RFC6418. However, that document talks > > > about the virtual interface *near-end* and does not talk > > > about the virtual link itself nor coordination with the > > > virtual interface *far-end(s)*. > > > > > > RFC6418, Section 3.8 is consistent with what the IRON > > > virtual interface near end expects, but IRON goes to > > > the full extent of describing coordinations between > > > the near end and any prospective far-ends. > > > > > > Thanks - Fred > > > fred.l.templin@boeing.com > > > > > > > -Hui > > > > > > > > > -----Original Message----- > > > > > From: Templin, Fred L [mailto:Fred.L.Templin@boeing.com] > > > > > Sent: Saturday, December 03, 2011 12:56 AM > > > > > To: Hui Deng; 'Andrew Sullivan' > > > > > Cc: mif@ietf.org > > > > > Subject: RE: [mif] IRON as a multiple interface solution > > > > > > > > > > Hi Hui, > > > > > > > > > > I am saying that IRON defines a new interface type > > > > > that would be one among possibly many interfaces of > > > > > a mif node. The properties of this interface type > > > > > include: > > > > > > > > > > - maintains stable network layer addresses even > > > > > if ISP connections change > > > > > - supports session continutity and fault tolerance > > > > > as ISP connections change > > > > > - avoids end user network renumbering when ISP > > > > > connections change in case the mif node acts > > > > > as a router > > > > > > > > > > There is more to it than just this, but the IRON > > > > > interface is another mif node interface type and > > > > > therefore needs to be taken under consideration, > > > > > e.g., for interface selection, source address > > > > > selection, etc. > > > > > > > > > > Thanks - Fred > > > > > fred.l.templin@boeing.com > > > > > > > > > > > -----Original Message----- > > > > > > From: Hui Deng [mailto:denghui@chinamobile.com] > > > > > > Sent: Friday, December 02, 2011 1:12 AM > > > > > > To: Templin, Fred L; 'Andrew Sullivan' > > > > > > Cc: mif@ietf.org > > > > > > Subject: RE: [mif] IRON as a multiple interface solution > > > > > > > > > > > > Hi Fred > > > > > > > > > > > > You are saying current MIF document is compatible with IRON. > > > > > > And current MIF document has already solved MIF's issues, > > > > > > so guess that IRON is proposing something else like generic > > > > > > internet access > > > > > > which is out of MIF. > > > > > > > > > > > > Regards, > > > > > > > > > > > > -Hui > > > > > > > > > > > > > -----Original Message----- > > > > > > > From: mif-bounces@ietf.org [mailto:mif-bounces@ietf.org] On > > > > > > Behalf Of > > > > > > > Templin, Fred L > > > > > > > Sent: Friday, December 02, 2011 4:10 AM > > > > > > > To: Andrew Sullivan > > > > > > > Cc: mif@ietf.org > > > > > > > Subject: Re: [mif] IRON as a multiple interface solution > > > > > > > > > > > > > > Hi Andrew, > > > > > > > > > > > > > > I took the time to go off and look at the mif wg > > > > > > > documents. All of it is good work - and all of it > > > > > > > is compatible with IRON. > > > > > > > > > > > > > > The mif documents talk about two primary classes of > > > > > > > interfaces: 1) ISP interfaces, and 2) VPN interfaces. > > > > > > > IRON introduces a third class of interface which > > > > > > > can be considered an "Internet interface". > > > > > > > > > > > > > > While it is true that most ISP interfaces provide > > > > > > > access to the Internet, ISP interfaces have volatile > > > > > > > configuration information that can change, e.g., if > > > > > > > the ISP point of connection changes. Conversely, the > > > > > > > IRON Internet interface has non-volatile configuration > > > > > > > information that remains the same even if the ISP > > > > > > > connections change (e.g., if the node is mobile). > > > > > > > > > > > > > > Since ISP interfaces may have access to private > > > > > > > namespaces, those interfaces (along with their > > > > > > > associated IP addresses) can be chosen for DNS > > > > > > > resolution and for accessing services within the > > > > > > > private namespace the same as described in the mif > > > > > > > documents. Since the IRON Internet interface has > > > > > > > a non-volatile configuration on the open Internet, > > > > > > > however, it provides a stable handle for default > > > > > > > communications with Internet-based correspondents. > > > > > > > > > > > > > > Again, this is all very compatible with the mif > > > > > > > work, and fits like a glove with what IRON expects. > > > > > > > > > > > > > > Thanks - Fred > > > > > > > fred.l.templin@boeing.com > > > > > > > > > > > > > > > -----Original Message----- > > > > > > > > From: Andrew Sullivan [mailto:ajs@anvilwalrusden.com] > > > > > > > > Sent: Monday, November 28, 2011 10:11 AM > > > > > > > > To: Templin, Fred L > > > > > > > > Cc: Hui Deng; Andrew Sullivan; mif@ietf.org > > > > > > > > Subject: Re: [mif] IRON as a multiple interface solution > > > > > > > > > > > > > > > > On Mon, Nov 28, 2011 at 09:22:45AM -0800, Templin, > > > > Fred L wrote: > > > > > > > > > That said, IRON does not preclude the host from > > accessing > > > > > > > > > services within the underlying ISP networks. To do so, > > > > > > > > > however, the host would have to use its ISP-delegated > > > > > > > > > address(es) and not the VSP-delegated address. > > > > > > > > > > > > > > > > > > Does this match your understanding? > > > > > > > > > > > > > > > > The central problem, however, is that if you are > > > > looking up the > > > > > > > > address for a name, you don't obviously know where it > > > > is (i.e. you > > > > > > > > don't know what network you need to go to). What I don't > > > > > > get in the > > > > > > > > IRON approach is how you cope with the fact that a user > > > > > > simply types > > > > > > > > some name into an application. We can't hardly ask them > > > > > > which network > > > > > > > > they want to use to look up the name. The MIF approach, > > > > > > as much as it > > > > > > > > makes me airsick, does address that issue. > > > > > > > > > > > > > > > > A > > > > > > > > > > > > > > > > -- > > > > > > > > Andrew Sullivan > > > > > > > > ajs@anvilwalrusden.com > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > mif mailing list > > > > > > > mif@ietf.org > > > > > > > https://www.ietf.org/mailman/listinfo/mif > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
- [mif] Motivations for draft-ietf-mif-dhcpv6-route… Maglione Roberta
- Re: [mif] Motivations for draft-ietf-mif-dhcpv6-r… teemu.savolainen
- Re: [mif] Motivations for draft-ietf-mif-dhcpv6-r… Ted Lemon
- [mif] Use cases for draft-ietf-mif-dhcpv6-route-o… Tomek Mrugalski
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Ted Lemon
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Keith Moore
- [mif] Use case 42 [Re: Use cases for draft-ietf-m… Brian E Carpenter
- Re: [mif] Use case 42 [Re: Use cases for draft-ie… Ted Lemon
- Re: [mif] Use case 42 [Re: Use cases for draft-ie… Brian E Carpenter
- Re: [mif] Use case 42 [Re: Use cases for draft-ie… Keith Moore
- Re: [mif] Use case 42 [Re: Use cases for draft-ie… Ted Lemon
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Alexandru Petrescu
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Alexandru Petrescu
- Re: [mif] Use case 42 [Re: Use cases for draft-ie… Alexandru Petrescu
- [mif] IRON as a multiple interface solution Templin, Fred L
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Ted Lemon
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Ted Lemon
- Re: [mif] IRON as a multiple interface solution Ted Lemon
- Re: [mif] IRON as a multiple interface solution Templin, Fred L
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Arifumi Matsumoto
- Re: [mif] IRON as a multiple interface solution Andrew Sullivan
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Brian E Carpenter
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Brian E Carpenter
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Ted Lemon
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Brian E Carpenter
- Re: [mif] IRON as a multiple interface solution Templin, Fred L
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Alexandru Petrescu
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Alexandru Petrescu
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Ted Lemon
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Ted Lemon
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Alexandru Petrescu
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Ted Lemon
- Re: [mif] IRON as a multiple interface solution Hui Deng
- Re: [mif] IRON as a multiple interface solution Templin, Fred L
- Re: [mif] IRON as a multiple interface solution Andrew Sullivan
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Tao Sun
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Tao Sun
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Lorenzo Colitti
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Brian E Carpenter
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Lorenzo Colitti
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Keith Moore
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… jouni korhonen
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Tao Sun
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Tao Sun
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Tao Sun
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Lorenzo Colitti
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Lorenzo Colitti
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Ted Lemon
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Alexandru Petrescu
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Ted Lemon
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Alexandru Petrescu
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Alexandru Petrescu
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Lorenzo Colitti
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Lorenzo Colitti
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Ted Lemon
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… jouni korhonen
- Re: [mif] IRON as a multiple interface solution Templin, Fred L
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… jouni korhonen
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Brian E Carpenter
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Lorenzo Colitti
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Brian E Carpenter
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Lorenzo Colitti
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Brian E Carpenter
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Ted Lemon
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Lorenzo Colitti
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… jouni korhonen
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Zhen Cao
- Re: [mif] IRON as a multiple interface solution Hui Deng
- Re: [mif] IRON as a multiple interface solution Templin, Fred L
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Tao Sun
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Tao Sun
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Tao Sun
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Tao Sun
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Lorenzo Colitti
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Lorenzo Colitti
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Lorenzo Colitti
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Jouni
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Brian E Carpenter
- Re: [mif] IRON as a multiple interface solution Hui Deng
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Lorenzo Colitti
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Jouni
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Alexandru Petrescu
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Alexandru Petrescu
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Tao Sun
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Lorenzo Colitti
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Tao Sun
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Jouni
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Lorenzo Colitti
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… pierrick.seite
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Tao Sun
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Tao Sun
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Lorenzo Colitti
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Alexandru Petrescu
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Ted Lemon
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Alexandru Petrescu
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Brian E Carpenter
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Jouni
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Brian E Carpenter
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Jouni
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Lorenzo Colitti
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Alexandru Petrescu
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Lorenzo Colitti
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Lorenzo Colitti
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Tao Sun
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Tao Sun
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Lorenzo Colitti
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Tao Sun
- Re: [mif] Use cases for draft-ietf-mif-dhcpv6-rou… Tao Sun
- Re: [mif] IRON as a multiple interface solution Hui Deng
- Re: [mif] IRON as a multiple interface solution Templin, Fred L
- Re: [mif] IRON as a multiple interface solution Templin, Fred L
- Re: [mif] IRON as a multiple interface solution Hui Deng
- Re: [mif] IRON as a multiple interface solution Hui Deng
- Re: [mif] IRON as a multiple interface solution Templin, Fred L
- Re: [mif] IRON as a multiple interface solution Hui Deng
- Re: [mif] IRON as a multiple interface solution Templin, Fred L
- [mif] New draft: IRON Applicability for Multiple … Templin, Fred L