IETF Logo Mail Archive

[OSPF] [OSPFv3-SR] Regarding Prefix SID Sub TLV advertisment for IPv6 data plane Segment routing

Veerendranatha Reddy Vallem <veerendranatharv@huawei.com> Mon, 16 January 2017 13:47 UTC

Return-Path: <veerendranatharv@huawei.com>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 102231294A9; Mon, 16 Jan 2017 05:47:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.419
X-Spam-Level:
X-Spam-Status: No, score=-7.419 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.199, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 ezW5gJwqDvtq; Mon, 16 Jan 2017 05:47:17 -0800 (PST)
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 768C6126B6D; Mon, 16 Jan 2017 05:47:16 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml704-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DEN89592; Mon, 16 Jan 2017 13:47:13 +0000 (GMT)
Received: from BLREML407-HUB.china.huawei.com (10.20.4.45) by lhreml704-cah.china.huawei.com (10.201.5.130) with Microsoft SMTP Server (TLS) id 14.3.301.0; Mon, 16 Jan 2017 13:47:10 +0000
Received: from BLREML501-MBX.china.huawei.com ([10.20.5.198]) by BLREML407-HUB.china.huawei.com ([10.20.4.45]) with mapi id 14.03.0301.000; Mon, 16 Jan 2017 19:16:16 +0530
From: Veerendranatha Reddy Vallem <veerendranatharv@huawei.com>
To: "'draft-ietf-ospf-ospfv3-segment-routing-extensions@ietf.org'" <'draft-ietf-ospf-ospfv3-segment-routing-extensions@ietf.org'>
Thread-Topic: [OSPFv3-SR] Regarding Prefix SID Sub TLV advertisment for IPv6 data plane Segment routing
Thread-Index: AdJv/tmvDD37OPTIRAu9eGFk3KJmrA==
Date: Mon, 16 Jan 2017 13:46:16 +0000
Message-ID: <73BFDDFFF499304EB26FE5FDEF20F78850865A6E@blreml501-mbx>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.18.152.243]
Content-Type: multipart/alternative; boundary="_000_73BFDDFFF499304EB26FE5FDEF20F78850865A6Eblreml501mbx_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020201.587CCEE2.0341, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=0.0.0.0, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 867a6830fc908a937d939b4d28e4f76b
Archived-At: <https://mailarchive.ietf.org/arch/msg/ospf/yGP5WepSD5dYtwXh7apJ-KppeJk>
Cc: "ospf@ietf.org" <ospf@ietf.org>
Subject: [OSPF] [OSPFv3-SR] Regarding Prefix SID Sub TLV advertisment for IPv6 data plane Segment routing
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Mon, 16 Jan 2017 13:47:19 -0000

Dear Authors,
I am requesting your clarification regarding prefix-SID sub TLV  advertisement for IPv6 data plane.

In case of data plane is IPV6 data plane,  while advertising IPv6 prefix (Node/Prefix SID) in E-intra/E-inter prefix TLV of extension LSAS, whether we need to include Prefix-SID sub TLV.
If need to include, we can encode  Ipv6 address prefix in SID/Label sub TLV. As per draft, if the length of this sub TLV must be 3 or 4.

For Adj-SID,  for SID filed it is clearly mention it may be ipv6 address, but it is not mentioned for Prefix- SID sub TLV.
It means for IPv6 prefix segment advertisement , Prefix-SID sub TLV  may not be required to advertise in extension LSAs.

Regards,
Veerendranath

v2.31.3 | Report a Bug | By Email | System Status