IETF Logo Mail Archive

Re: [spring] draft-bashandy-isis-srv6-extensions-05.txt

Peter Psenak <ppsenak@cisco.com> Wed, 13 March 2019 12:42 UTC

Return-Path: <ppsenak@cisco.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92D79130F0B; Wed, 13 Mar 2019 05:42:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -12.602
X-Spam-Level:
X-Spam-Status: No, score=-12.602 tagged_above=-999 required=5 tests=[DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-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 BXmm-H0vvQa1; Wed, 13 Mar 2019 05:42:48 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 481A2130FE5; Wed, 13 Mar 2019 05:42:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1592; q=dns/txt; s=iport; t=1552480967; x=1553690567; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=t9/OBh+xWYTgSI4ihOGT0MGyOfFHj5kThtz/hlK4KnI=; b=asjp/kftQfMOwxEO6Q4oyek47ZJuD+IqHabZP2ozJ9JTsFTAu1OEDlFG mWTyNY2dg236FE46zEb3K0OKYsefDCkUb4r4y0bB7pITPElhlOoZyh2bH NvAa7T+Rsm+mkDaeszRa1iH6heN+GrRHCReYnU3imbYiCaerU/MuJN19D g=;
X-IronPort-AV: E=Sophos;i="5.58,474,1544486400"; d="scan'208";a="10716747"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 13 Mar 2019 12:42:45 +0000
Received: from [10.147.24.38] ([10.147.24.38]) by aer-core-1.cisco.com (8.15.2/8.15.2) with ESMTP id x2DCgiif021047; Wed, 13 Mar 2019 12:42:45 GMT
To: Rajesh M <mrajesh@juniper.net>, "cfilsfil@cisco.com" <cfilsfil@cisco.com>, "abashandy.ietf@gmail.com" <abashandy.ietf@gmail.com>, "bruno.decraene@orange.com" <bruno.decraene@orange.com>, "huzhibo@huawei.com" <huzhibo@huawei.com>
References: <BYAPR05MB4821A77F5EAEC9C0F63349CABE4A0@BYAPR05MB4821.namprd05.prod.outlook.com>
Cc: Ron Bonica <rbonica@juniper.net>, SPRING WG <spring@ietf.org>, "ipv6@ietf.org" <ipv6@ietf.org>
From: Peter Psenak <ppsenak@cisco.com>
Message-ID: <cd7fd23b-819b-97d1-1cfb-332cae75b6e1@cisco.com>
Date: Wed, 13 Mar 2019 13:42:43 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <BYAPR05MB4821A77F5EAEC9C0F63349CABE4A0@BYAPR05MB4821.namprd05.prod.outlook.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Outbound-SMTP-Client: 10.147.24.38, [10.147.24.38]
X-Outbound-Node: aer-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/3uwl36yIQyudWvPqb5Crqa05OWI>
Subject: Re: [spring] draft-bashandy-isis-srv6-extensions-05.txt
X-BeenThere: spring@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <spring.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spring>, <mailto:spring-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring/>
List-Post: <mailto:spring@ietf.org>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spring>, <mailto:spring-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Mar 2019 12:42:54 -0000

Hi Rajesh,


On 13/03/2019 07:02 , Rajesh M wrote:
> 1)
>
> SRv6 Endpoint Function: 2 octets. As defined in
> [I-D.filsfils-spring-srv6-network-programming]
>
> Legal function values for this sub-TLV are defined in Section 7.
>
>
>
> This should be Section 8 I think, section 8 contains Advertising
> Endpoint Behaviors.
>
> Al reference to section 7 , we must change to section 8 (4 places)
>

fair enough, will fix that in the next version.

>
>
> 2)
>
>
>
> SRv6 Endpoint Function already mentions Endpoint Function Types.
>
>
>
> SIDusually will be a combination of Locator:Function:ARGS.
>
>
>
> Since SID already contains Function, why there is a need for additional
> SRv6 Endpoint Function field ? Am I missing something.


SRv6 Endpoint Function represents the behavior, which comes from
"SRv6 Endpoint Behaviors Registry". That value is not present in the 128 
bits SID value, which is locally assigned by the advertising node.

thanks,
Peter





>
>
>
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> | Flags | SRv6 Endpoint Function |
>
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> | SID (128 bits) . . . |
>
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> | SID (cont . . .) |
>
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> | SID (cont . . .) |
>
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> | SID (cont . . .) |
>
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>
>

v2.23.0 | Report a Bug | By Email