IETF Logo Mail Archive

[OSPF] [OSPFv3 IPv6 SR] Regarding prefixes identification for IPv6 Segment Routing

Veerendranatha Reddy Vallem <veerendranatharv@huawei.com> Tue, 14 February 2017 07:39 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 4E0EC1294EF; Mon, 13 Feb 2017 23:39:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 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=-0.001, 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 w9MuYlBfUOTz; Mon, 13 Feb 2017 23:39:31 -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 C47921294A9; Mon, 13 Feb 2017 23:39:30 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml702-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DGL23414; Tue, 14 Feb 2017 07:39:28 +0000 (GMT)
Received: from LHREML712-CAH.china.huawei.com (10.201.108.35) by lhreml702-cah.china.huawei.com (10.201.5.99) with Microsoft SMTP Server (TLS) id 14.3.301.0; Tue, 14 Feb 2017 07:38:28 +0000
Received: from BLREML408-HUB.china.huawei.com (10.20.4.47) by LHREML712-CAH.china.huawei.com (10.201.108.35) with Microsoft SMTP Server (TLS) id 14.3.301.0; Tue, 14 Feb 2017 07:38:27 +0000
Received: from BLREML501-MBX.china.huawei.com ([10.20.5.198]) by BLREML408-HUB.china.huawei.com ([10.20.4.47]) with mapi id 14.03.0301.000; Tue, 14 Feb 2017 13:08:22 +0530
From: Veerendranatha Reddy Vallem <veerendranatharv@huawei.com>
To: "draft-ietf-ospf-ospfv3-lsa-extend.authors@ietf.org" <draft-ietf-ospf-ospfv3-lsa-extend.authors@ietf.org>
Thread-Topic: [OSPFv3 IPv6 SR] Regarding prefixes identification for IPv6 Segment Routing
Thread-Index: AdKGlFksyjOSP5PBTr6bWApBsa9BeQ==
Date: Tue, 14 Feb 2017 07:38:22 +0000
Message-ID: <73BFDDFFF499304EB26FE5FDEF20F7885087171F@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_73BFDDFFF499304EB26FE5FDEF20F7885087171Fblreml501mbx_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090202.58A2B431.0056, 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: 1592f10688566b1543f099b16640eaa7
Archived-At: <https://mailarchive.ietf.org/arch/msg/ospf/DnUIsd2QqYZk45zGqOYzeWAyQLM>
Cc: "ospf@ietf.org" <ospf@ietf.org>
Subject: [OSPF] [OSPFv3 IPv6 SR] Regarding prefixes identification for IPv6 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: Tue, 14 Feb 2017 07:39:33 -0000

Dear Authors,
While adverting prefixes for IPv6 Segment Routing (SRH support), the IPv6 prefixes  may not require to carry additional sub TLVs related to SRH some times.
So to identify prefixes are using for IPv6 Segment Routing, it may be helpful we add one option bit in prefix options like 'N' bit added for Node identification.

Please provide your opinion for adding new bit for IPv6 segment routing  in prefix options.

                        0  1  2  3  4  5  6  7
                    +--+--+--+--+--+--+--+--+
                    |  |  | N|DN| P| x|LA|NU|
                    +--+--+--+--+--+--+--+--+

Regards,
Veerendranath

v2.23.0 | Report a Bug | By Email