IETF Logo Mail Archive

Re: [OSPF] Comments draft-ietf-ospf-segment-routing-extensions-00.txt

Xuxiaohu <xuxiaohu@huawei.com> Thu, 03 July 2014 10:02 UTC

Return-Path: <xuxiaohu@huawei.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 7AA9F1A04AC for <ospf@ietfa.amsl.com>; Thu, 3 Jul 2014 03:02:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.852
X-Spam-Level:
X-Spam-Status: No, score=-4.852 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] 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 3JW8a_Rr23uL for <ospf@ietfa.amsl.com>; Thu, 3 Jul 2014 03:02:00 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 02FDE1A0368 for <ospf@ietf.org>; Thu, 3 Jul 2014 03:01:59 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml402-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BJO02717; Thu, 03 Jul 2014 10:01:58 +0000 (GMT)
Received: from NKGEML401-HUB.china.huawei.com (10.98.56.32) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 3 Jul 2014 11:01:58 +0100
Received: from NKGEML512-MBS.china.huawei.com ([169.254.8.48]) by nkgeml401-hub.china.huawei.com ([10.98.56.32]) with mapi id 14.03.0158.001; Thu, 3 Jul 2014 18:01:53 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: Peter Psenak <ppsenak@cisco.com>, Acee Lindem <acee.lindem@ericsson.com>
Thread-Topic: [OSPF] Comments draft-ietf-ospf-segment-routing-extensions-00.txt
Thread-Index: AQHPlem4IpA14m6HCEObXOqvma7kYJuMgQWAgAD5SACAAJ7xwA==
Date: Thu, 03 Jul 2014 10:01:52 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0828FF4C@NKGEML512-MBS.china.huawei.com>
References: <948E8138-3BB5-4292-9CF6-4131F6AEED8D@ericsson.com> <53B3EE66.90608@cisco.com> <677E5EF6-C3F0-41DB-A7DA-7C43E07E3B07@ericsson.com> <53B50FBC.60803@cisco.com>
In-Reply-To: <53B50FBC.60803@cisco.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.98.134]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/ospf/al_ujGn4PAMrbbzYK4Eesaax7Hg
Cc: OSPF List <ospf@ietf.org>
Subject: Re: [OSPF] Comments draft-ietf-ospf-segment-routing-extensions-00.txt
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: Thu, 03 Jul 2014 10:02:01 -0000


> -----Original Message-----
> From: OSPF [mailto:ospf-bounces@ietf.org] On Behalf Of Peter Psenak
> Sent: Thursday, July 03, 2014 4:10 PM
> To: Acee Lindem
> Cc: OSPF List
> Subject: Re: [OSPF] Comments
> draft-ietf-ospf-segment-routing-extensions-00.txt
> 
> Hi Acee,
> 
> please see inline:
> 
> On 7/2/14 19:17 , Acee Lindem wrote:
> > Hi Peter,
> > It seems there are two distinct deployment scenarios - one where SR routers
> are given a range and policy and allocate their own SIDs and another where a
> mapping server does it for the routing domain.
> 
> yes, that is correct. The latter is used mainly during migration from LDP to SR.

The mapping server could actually be used to advertise global SIDs for all the SR-capable nodes as well (see http://tools.ietf.org/html/draft-xu-ospf-global-label-sid-adv-00). In this way, the potential risk of global SID allocation collision can be avoided. 

Best regards,
Xiaohu

v2.23.0 | Report a Bug | By Email