IETF Logo Mail Archive

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

Peter Psenak <ppsenak@cisco.com> Mon, 27 February 2017 15:01 UTC

Return-Path: <ppsenak@cisco.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 C792C12A0B2; Mon, 27 Feb 2017 07:01:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level:
X-Spam-Status: No, score=-14.522 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 4E1z_VhQdc5T; Mon, 27 Feb 2017 07:01:56 -0800 (PST)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A326C12A0AD; Mon, 27 Feb 2017 07:01:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1556; q=dns/txt; s=iport; t=1488207716; x=1489417316; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=rmxOp7fAsClrYsQtnl6rCSeX8OLN2kfePLkoBuGuxk0=; b=GDRi9rEKINey+++cgvpyQ3uHtRCf1TDG613jtjZG0E31SE7rBy3J+Rag LU/VozaZ9YpOEuFr7ya77M+IYoZnZ1C9Hf3WJfQsOveOR5ZUP6HfyO3SP vXaczMqYPb0tnG/z43eaCxEZE7djxHCeuV2K7LlDLswTcDdpNcmPH2JF+ Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CdBQCIPrRY/xbLJq1UChkBAQEBAQEBAQEBAQcBAQEBAYQ0gQaOVpBtl0KCRwGDVQMCAoJdFQECAQEBAQEBAWIohHABAQEEDCYBBUABEAsRBAEBAQkWDwkDAgECATwBCAYBDAEFAgEBiXCyEhKLPQEBAQEBAQEBAQEBAQEBAQEBAQEBAR2GTIRvhCwLAQGGAAEEnB6SJ4F7hSCDMIZNkzE1IoEBIRQIFxWFQ4FJPzWHbIIuAQEB
X-IronPort-AV: E=Sophos;i="5.35,215,1484006400"; d="scan'208";a="652847975"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 27 Feb 2017 15:01:53 +0000
Received: from [10.61.196.105] ([10.61.196.105]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id v1RF1qCA018787; Mon, 27 Feb 2017 15:01:53 GMT
Message-ID: <58B43F60.8080009@cisco.com>
Date: Mon, 27 Feb 2017 16:01:52 +0100
From: Peter Psenak <ppsenak@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Veerendranatha Reddy Vallem <veerendranatharv@huawei.com>, "draft-ietf-ospf-ospfv3-lsa-extend.authors@ietf.org" <draft-ietf-ospf-ospfv3-lsa-extend.authors@ietf.org>, "draft-ietf-ospf-ospfv3-segment-routing-extensions@ietf.org" <draft-ietf-ospf-ospfv3-segment-routing-extensions@ietf.org>
References: <73BFDDFFF499304EB26FE5FDEF20F78850873AA8@blreml501-mbx>
In-Reply-To: <73BFDDFFF499304EB26FE5FDEF20F78850873AA8@blreml501-mbx>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ospf/GAXcdcJwN-8muIsvr391sqYKMn0>
Cc: "ospf@ietf.org" <ospf@ietf.org>
Subject: Re: [OSPF] FW: [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: Mon, 27 Feb 2017 15:01:58 -0000

Veerendranath,

can you please elaborate on the use case? I'm not sure I understand 
exactly what you are asking for.

thanks,
Peter

On 20/02/17 10:34 , Veerendranatha Reddy Vallem wrote:
> Dear Authors,
>
> Gentle remainder,
>
> We are planning to implement the “identification of IPv6 prefix for
> segment routings  (SRH) by setting the flag in option field” as
> described in below mail.
>
> Please provide your valuable opinion  whether it is ok as per Extension
> draft.
>
> Regards,
>
> Veerendranath
>
> *From:* Veerendranatha Reddy Vallem
> *Sent:* 14 February 2017 13:08
> *To:* 'draft-ietf-ospf-ospfv3-lsa-extend.authors@ietf.org'
> <draft-ietf-ospf-ospfv3-lsa-extend.authors@ietf.org>
> *Cc:* ospf@ietf.org
> *Subject:* [OSPFv3 IPv6 SR] Regarding prefixes identification for IPv6
> Segment Routing
>
> 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