IETF Logo Mail Archive

Re: [v6ops] I-D Action:draft-ietf-v6ops-ipv6-cpe-router-bis-00.txt

"Hemant Singh (shemant)" <shemant@cisco.com> Tue, 22 March 2011 23:43 UTC

Return-Path: <shemant@cisco.com>
X-Original-To: v6ops@core3.amsl.com
Delivered-To: v6ops@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A389F28C179 for <v6ops@core3.amsl.com>; Tue, 22 Mar 2011 16:43:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.699
X-Spam-Level:
X-Spam-Status: No, score=-10.699 tagged_above=-999 required=5 tests=[AWL=-0.100, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ki-ErDgvqHcC for <v6ops@core3.amsl.com>; Tue, 22 Mar 2011 16:43:10 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id 652F828C178 for <v6ops@ietf.org>; Tue, 22 Mar 2011 16:43:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=shemant@cisco.com; l=2542; q=dns/txt; s=iport; t=1300837484; x=1302047084; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=h6ilbU0aoe23hoM2ICCV20FubLG0CRAxHIfEfsmkBb0=; b=aRZWIE/rp9gDNuTKznJXeXlfIpR47DPMEe2BwBCc4pslJ1sBbpICr1a3 9THK4aXjQ7N0RcMmn0M4AnyLYnEj0XmQ305a7xJGWHOLK6NeDDN55VQ6S UAYibT8aVnfgVGXQc6qPEbn5i1Ksx7u59jIaipruWhooD5EhHQI2BxDcZ k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4AAB/RiE2tJXG+/2dsb2JhbACERZNHjFdfd6kpizaQWIEng0p3BIU1iw6DIg
X-IronPort-AV: E=Sophos;i="4.63,228,1299456000"; d="scan'208";a="669635832"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by sj-iport-6.cisco.com with ESMTP; 22 Mar 2011 23:44:43 +0000
Received: from xbh-rcd-201.cisco.com (xbh-rcd-201.cisco.com [72.163.62.200]) by rcdn-core2-3.cisco.com (8.14.3/8.14.3) with ESMTP id p2MNihv5023690; Tue, 22 Mar 2011 23:44:43 GMT
Received: from xmb-rcd-109.cisco.com ([72.163.62.151]) by xbh-rcd-201.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 22 Mar 2011 18:44:43 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: base64
Date: Tue, 22 Mar 2011 18:44:20 -0500
Message-ID: <5B6B2B64C9FE2A489045EEEADDAFF2C3011831B0@XMB-RCD-109.cisco.com>
In-Reply-To: <4D89233D.6070309@gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [v6ops] I-D Action:draft-ietf-v6ops-ipv6-cpe-router-bis-00.txt
Thread-Index: Acvo4OdRYwj7l9gRSHGuU4vmK0OzXQAB4oSA
References: <20110305184502.18531.25548.idtracker@localhost> <C895B643-E461-4191-BAC3-EF735311F2F0@apple.com> <5B6B2B64C9FE2A489045EEEADDAFF2C3F8B9B0@XMB-RCD-109.cisco.com><E76372ED-41A1-4987-9ECF-888B285DD606@apple.com> <4D7E685A.80202@bogus.com> <5B6B2B64C9FE2A489045EEEADDAFF2C301049872@XMB-RCD-109.cisco.com> <alpine.DEB.2.00.1103152011560.4842@uplift.swm.pp.se> <5B6B2B64C9FE2A489045EEEADDAFF2C301049924@XMB-RCD-109.cisco.com> <4D7FE427.7000201@gmail.com> <5B6B2B64C9FE2A489045EEEADDAFF2C30104A0ED@XMB-RCD-109.cisco.com> <4D8260E2.2080600@gmail.com> <alpine.DEB.2.00.1103172035400.4842@uplift.swm.pp.se><m1Q0gaW-0001gmC@stereo.hq.phicoh.net> <3179B83D-003E-4619-96F8-622E27752EC3@cisco.com> <alpine.DEB.2.00.1103182204030.4842@uplift.swm.pp.se> <C1366B36-15E1-4E98-AED4-D95FD003793C@cisco.com><alpine.DEB.2.00.1103190558280.4842@uplift.swm.pp.se> <4D85053C.8040904@gmail.com> <5B6B2B64C9FE2A489045EEEADDAFF2C301183090@XMB-RCD-109.cisco.com> <4D89233D.6070309@gmail.com>
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-OriginalArrivalTime: 22 Mar 2011 23:44:43.0826 (UTC) FILETIME=[1E957120:01CBE8EB]
Cc: IPv6 Ops WG <v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action:draft-ietf-v6ops-ipv6-cpe-router-bis-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Mar 2011 23:43:11 -0000

-----Original Message-----
From: Brian E Carpenter [mailto:brian.e.carpenter@gmail.com] 
Sent: Tuesday, March 22, 2011 6:31 PM
To: Hemant Singh (shemant)
Cc: Mikael Abrahamsson; IPv6 Ops WG
Subject: Re: [v6ops] I-D Action:draft-ietf-v6ops-ipv6-cpe-router-bis-00.txt


>I agree. BRDP is far from cooked as an IETF solution. Shim6 is standardised,
>but requires no special action by the CE router anyway.

Ah, OK.  Sorry, I am behind on my reading and shim6 is one specification I have to go thru.  Anyone deploy shim6 yet in any SP/edge network?

>I assume you are now talking about a future draft and not about
>cpe-router-bis?

I do think so - draft-cpe-router-ter should deal with multihoming and graphed routed topologies.  The reason is because the bis document is gestating to a critical mass for new requirements that would be worth publishing.  The routing section in section 5.4 has reached rough consensus in this mailer for text.  DNS is something we have to work on a bit.  Thereafter we could submit the bis document for LastCall.

>Again - this topic (and your analysis, if it's correct) seems to me to
>belong in the multihoming-without-nat66 draft.

Ah, OK.  

>As I said a long time ago when MIF was first discussed, it seems that what
>we need is to replace the concept of "default router" in the host stack
>with a concept of "default router per prefix".

When a host has to forward a packet to a destination, the destination is either on-link (if the destination matches a prefix in the host's ND Prefix List) or off-link that means the packet is shipped to default router(s).  Thus all I can see is a default routers(s) per destination, not prefix.   Note the MSR is a construct that can map a prefix to a default router where the default router in the router that sent the RA with the MSR. 

Hemant

v2.23.0 | Report a Bug | By Email