[IPv6 SR] Regarding 128 bits IPv6 address in Segment List of SRH

Veerendranatha Reddy Vallem <veerendranatharv@huawei.com> Thu, 09 February 2017 16:02 UTC

Return-Path: <veerendranatharv@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8A1E129B30; Thu, 9 Feb 2017 08:02:37 -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 dcPlfAyz-S2K; Thu, 9 Feb 2017 08:02:35 -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 D4738129B32; Thu, 9 Feb 2017 08:02:30 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml703-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DAH58015; Thu, 09 Feb 2017 16:02:28 +0000 (GMT)
Received: from BLREML703-CAH.china.huawei.com (10.20.4.172) by lhreml703-cah.china.huawei.com (10.201.5.104) with Microsoft SMTP Server (TLS) id 14.3.301.0; Thu, 9 Feb 2017 16:02:27 +0000
Received: from BLREML501-MBX.china.huawei.com ([10.20.5.198]) by blreml703-cah.china.huawei.com ([::1]) with mapi id 14.03.0301.000; Thu, 9 Feb 2017 21:32:20 +0530
From: Veerendranatha Reddy Vallem <veerendranatharv@huawei.com>
To: "draft-ietf-6man-segment-routing-header@ietf.org" <draft-ietf-6man-segment-routing-header@ietf.org>, "draft-ietf-ospf-ospfv3-segment-routing-extensions@tools.ietf.org" <draft-ietf-ospf-ospfv3-segment-routing-extensions@tools.ietf.org>
Subject: [IPv6 SR] Regarding 128 bits IPv6 address in Segment List of SRH
Thread-Topic: [IPv6 SR] Regarding 128 bits IPv6 address in Segment List of SRH
Thread-Index: AdKC3shnNhYwdbbrRSWzOM8TNO3Pyg==
Date: Thu, 9 Feb 2017 16:02:19 +0000
Message-ID: <73BFDDFFF499304EB26FE5FDEF20F7885086FA74@blreml501-mbx>
Accept-Language: en-US
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_73BFDDFFF499304EB26FE5FDEF20F7885086FA74blreml501mbx_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090202.589C9295.0015, 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: 2f47716fd34fdd3b11a474aa1b29339f
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/6jFk0IRMLimU9G0nKPcNihxvGUc>
Cc: "ospf@ietf.org" <ospf@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Feb 2017 16:02:38 -0000

Dear Authors,

I am requesting your clarification regarding usage of Adj-SID in SRH header.



As per draft, the segment list  is the list of 128 bit IPv6 address.

Whether it means it is global ipv6 address or can be link local address also.


As per "OSPFv3 Extensions for Segment Routing" draft, the Adj-SID can be link local address.

In section 7.1,





    0                   1                   2                   3

    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1

   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   |               Type            |              Length           |

   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   | Flags         |     Weight    |             Reserved          |

   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   |                   SID/Label/Index (variable)                  |

   +---------------------------------------------------------------+



Examples:



            A 32 bit global index defining the offset in the SID/Label

            space advertised by this router - in this case the V and L

            flags MUST NOT be set.



            A 24 bit local label where the 20 rightmost bits are used

            for encoding the label value - in this case the V and L

            flags MUST be set.



            16 octet IPv6 address - in this case the V-flag MUST be set.

            The L-flag MUST be set for link-local IPv6 address and MUST

            NOT be set for IPv6 global unicast address.



If Link local address is Link local, how we can use this address in SRH header,

since IPv6 destination address should not be link local address as per IPv6 protocol.



If Adj-Sid is global ipv6 address, means we need to consider "global ipv6 interface address" of the neighbor on the link?



Regards,

Veerendranath