Re: [OSPF] 答复: [Isis-wg] 答复: 答复: [sunset4] IPv6 router IDs

"Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com> Fri, 30 May 2014 03:21 UTC

Return-Path: <manav.bhatia@alcatel-lucent.com>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8F8B1A06F9; Thu, 29 May 2014 20:21:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.6
X-Spam-Level:
X-Spam-Status: No, score=-6.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-5] 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 hw8IVdHLE0-j; Thu, 29 May 2014 20:20:59 -0700 (PDT)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 860161A02E8; Thu, 29 May 2014 20:20:59 -0700 (PDT)
Received: from us70tusmtp1.zam.alcatel-lucent.com (h135-5-2-63.lucent.com [135.5.2.63]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id s4U3KWOF029343 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 29 May 2014 22:20:33 -0500 (CDT)
Received: from US70TWXCHHUB04.zam.alcatel-lucent.com (us70twxchhub04.zam.alcatel-lucent.com [135.5.2.36]) by us70tusmtp1.zam.alcatel-lucent.com (GMO) with ESMTP id s4U3KUPT018043 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 29 May 2014 23:20:31 -0400
Received: from SG70XWXCHHUB02.zap.alcatel-lucent.com (135.253.2.47) by US70TWXCHHUB04.zam.alcatel-lucent.com (135.5.2.36) with Microsoft SMTP Server (TLS) id 14.2.247.3; Thu, 29 May 2014 23:20:31 -0400
Received: from SG70YWXCHMBA05.zap.alcatel-lucent.com ([169.254.5.252]) by SG70XWXCHHUB02.zap.alcatel-lucent.com ([135.253.2.47]) with mapi id 14.02.0247.003; Fri, 30 May 2014 11:20:28 +0800
From: "Bhatia, Manav (Manav)" <manav.bhatia@alcatel-lucent.com>
To: Acee Lindem <acee.lindem@ericsson.com>, Xuxiaohu <xuxiaohu@huawei.com>
Thread-Topic: [OSPF] 答复: [Isis-wg] 答复: 答复: [sunset4] IPv6 router IDs
Thread-Index: AQHPbeep0KeJfDl/fkGY3udMB/Ik+ZtYizLg
Date: Fri, 30 May 2014 03:20:27 +0000
Message-ID: <20211F91F544D247976D84C5D778A4C32E621EA5@SG70YWXCHMBA05.zap.alcatel-lucent.com>
References: <CF961C89.2DC41%acee.lindem@ericsson.com>
In-Reply-To: <CF961C89.2DC41%acee.lindem@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.253.19.17]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ospf/bA5VFH5TdXBF7Fq0L1VNN60Jdl4
Cc: "isis-wg@ietf.org" <isis-wg@ietf.org>, "fanpeng@chinamobile.com" <fanpeng@chinamobile.com>, Wes George <wesley.george@twcable.com>, Joel jaeggli <joelja@bogus.com>, OSPF List <ospf@ietf.org>, "sunset4@ietf.org" <sunset4@ietf.org>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "lizhenqiang@chinamobile.com" <lizhenqiang@chinamobile.com>
Subject: Re: [OSPF] 答复: [Isis-wg] 答复: 答复: [sunset4] IPv6 router IDs
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ospf/>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 May 2014 03:21:02 -0000

Sorry for joining the party so late ..

Those of you following the BFD WG would know that BFD WG is currently being re-chartered to include S-BFD as one of the items that it will be working on.

For S-BFD to work, we need to distribute the S-BFD discriminators across the IGP routing domain. How this can be achieved with OSPF has been described in http://tools.ietf.org/id/draft-bhatia-ospf-sbfd-discriminator-00.txt

With the help of this draft S-BFD clients will know what S-BFD discriminator to use when talking to the reflector or the S-BFD server.

However, it still needs a routable IP address that it can use to set up the S-BFD session.

I believe the draft http://tools.ietf.org/html/draft-xu-ospf-ipv6-router-id-00 will help us in getting that information in the IPv6 context.

Unfortunately, the above draft uses an inappropriate TLV name and doesn’t seem to have a use-case that supports the need for such a TLV. I believe we have at least one use case where we need a "routable" IPv6 address. 

Cheers, Manav

> -----Original Message-----
> From: OSPF [mailto:ospf-bounces@ietf.org] On Behalf Of Acee Lindem
> Sent: Monday, May 12, 2014 7:10 PM
> To: Xuxiaohu
> Cc: isis-wg@ietf.org; Wes George; fanpeng@chinamobile.com; Joel
> jaeggli; OSPF List; sunset4@ietf.org; lizhenqiang@chinamobile.com
> Subject: Re: [OSPF] 答复: [Isis-wg] 答复: 答复: [sunset4] IPv6 router
> IDs
> 
> Hi Xiaohu,
> Please include the precise use cases as to WHY this is needed OSPF
> draft.
> And by precise, I don't mean just listing MPLS applications, I mean
> explaining why you need this routable address above and beyond what is
> already advertised. At least in the case of OSPF, I'm not convinced.
> Thanks,
> Acee
> 
> 
> -----Original Message-----
> From: Xuxiaohu <xuxiaohu@huawei.com>
> Date: Sunday, May 11, 2014 6:44 PM
> To: Ericsson <acee.lindem@ericsson.com>
> Cc: Karsten Thomann <karsten_thomann@linfre.de>, Anton Smirnov
> <asmirnov@cisco.com>, "isis-wg@ietf.org" <isis-wg@ietf.org>,
> "fanpeng@chinamobile.com" <fanpeng@chinamobile.com>, Wes George
> <wesley.george@twcable.com>, Joel jaeggli <joelja@bogus.com>, OSPF -
> OSPF
> WG List <ospf@ietf.org>, "sunset4@ietf.org" <sunset4@ietf.org>,
> "lizhenqiang@chinamobile.com" <lizhenqiang@chinamobile.com>
> Subject: 答复: [Isis-wg] [OSPF] 答复:  答复:  [sunset4]   IPv6 router
> IDs
> 
> >Hi Acee,
> >
> >IMHO, segment routing could work together with the RFC3464 VPN. In
> such
> >case, the segment routing just replace the role of LDP or RSVP-TE of
> >establishing a transport LSP between PE routers.
> >
> >Best regards,
> >Xiaohu