Re: [mif] I-D Action: draft-baker-6man-multi-homed-host-00.txt

Liang Geng <liang.geng@hotmail.com> Sat, 26 September 2015 15:06 UTC

Return-Path: <liang.geng@hotmail.com>
X-Original-To: mif@ietfa.amsl.com
Delivered-To: mif@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AD3D1B2EDF for <mif@ietfa.amsl.com>; Sat, 26 Sep 2015 08:06:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.71
X-Spam-Level:
X-Spam-Status: No, score=-0.71 tagged_above=-999 required=5 tests=[FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SShslrOaOx6V for <mif@ietfa.amsl.com>; Sat, 26 Sep 2015 08:06:33 -0700 (PDT)
Received: from SNT004-OMC2S52.hotmail.com (snt004-omc2s52.hotmail.com [65.54.61.103]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8C2D81B2EDC for <mif@ietf.org>; Sat, 26 Sep 2015 08:06:33 -0700 (PDT)
Received: from SNT153-DS25 ([65.55.90.71]) by SNT004-OMC2S52.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Sat, 26 Sep 2015 08:05:32 -0700
X-TMN: [gj79An7xjJLC8zGL8g2IKmOxCXtavy0G]
X-Originating-Email: [liang.geng@hotmail.com]
Message-ID: <SNT153-DS25277E7E4A83AE74CDCAA887410@phx.gbl>
From: Liang Geng <liang.geng@hotmail.com>
To: "'Fred Baker (fred)'" <fred@cisco.com>
References: <20150807144043.10132.18362.idtracker@ietfa.amsl.com> <01A096FF-9E7E-406E-BE2E-14EDB99A2D2D@cisco.com> <SNT153-DS19CF43DD33F54D5FB0162587470@phx.gbl> <4A6D5DCB-AD7D-45DE-AB54-8001F111F6C2@cisco.com>
In-Reply-To: <4A6D5DCB-AD7D-45DE-AB54-8001F111F6C2@cisco.com>
Date: Sat, 26 Sep 2015 23:05:29 +0800
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AQHQ94RuCkdTkr3P+U2YcUmDjc/Idp5O3e7g
Content-Language: zh-cn
X-OriginalArrivalTime: 26 Sep 2015 15:05:32.0580 (UTC) FILETIME=[CA2C4640:01D0F86C]
Archived-At: <http://mailarchive.ietf.org/arch/msg/mif/lmWYORLaLpUsy0gio2ZEZ7qfork>
Cc: mif@ietf.org
Subject: Re: [mif] I-D Action: draft-baker-6man-multi-homed-host-00.txt
X-BeenThere: mif@ietf.org
X-Mailman-Version: 2.1.15
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: <https://mailarchive.ietf.org/arch/browse/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: Sat, 26 Sep 2015 15:06:38 -0000

Dear Fred,

Thank you for your email.

I received your request for comments in MIF mail list and my previous email was a response of that.

I believe that this draft describes the behavior of a host very similar to the host which behaves as a MPVD-aware node in MIF. I might get this wrong but I suspect that the related MIF RFCs (i.e. RFC 7556) may have covered the same issues.

Therefore, I think It is very important for us to understand whether and how much of this work is in MIF or 6MAN's scope and how it should fit in to avoid any duplication. Currently without seeing much conflict on how multi-homed host/network behavior is described in both your draft and MIF architecture, I am a bit worried that there might be some extent of overlaps. Hence, I would also like to see more comments both from your side and mif folks.

Best wishes,
Liang 
> -----Original Message-----
> From: Fred Baker (fred) [mailto:fred@cisco.com]
> Sent: Friday, September 25, 2015 7:22 PM
> To: Liang Geng
> Cc: mif@ietf.org; Brian E Carpenter
> Subject: Re: [mif] I-D Action: draft-baker-6man-multi-homed-host-00.txt
> 
> Thanks. I'm not just sure why you copied me and not my co-author, but
> whatever. Yes, I think they are related problems. I'm glad you see no conflict; if
> you see an issue, please let us know.
> 
> > On Sep 20, 2015, at 9:14 AM, Liang Geng <liang.geng@hotmail.com> wrote:
> >
> > Hi Fred,
> >
> > I have just read through this draft (the most recent 03 version).
> >
> > The draft is very pleasant to read and I believe it focuses on the
> > same multi-homed issue MIF WG is working on. It very well described
> > how IPV6 hosts/network are expected to behave in multi-homed scenario.
> >
> > In mif, Provisioning Domain (PvD) is introduced to associate and
> > identify network configurations for a particular interface. I think it
> > is a good idea to see if there is any conflict between the mechanism
> > in PvD solution and the host/network behavior described in your draft.
> > However, I don't see obvious ones at present.
> >
> > Best wishes,
> > Liang
> >
> >> -----邮件原件-----
> >> 发件人: mif [mailto:mif-bounces@ietf.org] 代表 Fred Baker (fred)
> >> 发送时间: 2015年8月10日 22:04
> >> 收件人: mif@ietf.org
> >> 主题: [mif] Fwd: I-D Action: draft-baker-6man-multi-homed-host-00.txt
> >>
> >> This is actually being discussed in 6man, as the chairs requested it
> > there, but
> >> MIF might have comments to pass along.
> >>
> >>> Begin forwarded message:
> >>>
> >>> From: <internet-drafts@ietf.org>
> >>> Subject: I-D Action: draft-baker-6man-multi-homed-host-00.txt
> >>> Date: August 7, 2015 at 7:40:43 AM PDT
> >>> To: <i-d-announce@ietf.org>
> >>> Reply-To: <internet-drafts@ietf.org>
> >>>
> >>>
> >>> A New Internet-Draft is available from the on-line Internet-Drafts
> >> directories.
> >>>
> >>>
> >>>     Title           : Host routing in a multi-prefix network
> >>>     Authors         : Fred Baker
> >>>                       Brian Carpenter
> >>> 	Filename        : draft-baker-6man-multi-homed-host-00.txt
> >>> 	Pages           : 6
> >>> 	Date            : 2015-08-07
> >>>
> >>> Abstract:
> >>> This note describes expected host behavior in a network that has
> >>> more than one prefix, each allocated by an upstream network that
> >>> implements BCP 38 filtering.
> >>>
> >>>
> >>> The IETF datatracker status page for this draft is:
> >>> https://datatracker.ietf.org/doc/draft-baker-6man-multi-homed-host/
> >>>
> >>> There's also a htmlized version available at:
> >>> https://tools.ietf.org/html/draft-baker-6man-multi-homed-host-00
> >>>
> >>>
> >>> Please note that it may take a couple of minutes from the time of
> >>> submission until the htmlized version and diff are available at
> > tools.ietf.org.
> >>>
> >>> Internet-Drafts are also available by anonymous FTP at:
> >>> ftp://ftp.ietf.org/internet-drafts/
> >>>
> >>> _______________________________________________
> >>> I-D-Announce mailing list
> >>> I-D-Announce@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/i-d-announce
> >>> Internet-Draft directories: http://www.ietf.org/shadow.html or
> >>> ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> >
> >