[Lsr] clarification of locator block and locator node in draft-ietf-spring-srv6-network-programming and draft-ietf-lsr-isis-srv6-extensions

Chris Bowers <chrisbowers.ietf@gmail.com> Thu, 27 February 2020 17:18 UTC

Return-Path: <chrisbowers.ietf@gmail.com>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A23F63A0D6A; Thu, 27 Feb 2020 09:18:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 qipfDdIdnM7O; Thu, 27 Feb 2020 09:18:40 -0800 (PST)
Received: from mail-qv1-xf35.google.com (mail-qv1-xf35.google.com [IPv6:2607:f8b0:4864:20::f35]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 163583A0D69; Thu, 27 Feb 2020 09:18:40 -0800 (PST)
Received: by mail-qv1-xf35.google.com with SMTP id bo12so1034478qvb.13; Thu, 27 Feb 2020 09:18:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=R9lR+T+it4zXhO0VHI513uRYuauDnEwKY8nbzxlXDBk=; b=KTzPfuVQSRiTIHU3aTyFcLgtSRFdb+QBSVT/Oo76EJEWYE/TgxerEwAn2G5HDgaKYk 8X58Gl+ghuSdqJobIDjGOwQdX4KqRBknYImoCX2NL2T7/CLYfDti4AAf67G8n6mwAv4q YU382ywi9O5K5Taha6VJP+NMwy/rs3Z8eZiMtTatUMZ+4rFehKb4sfZB0hLfzPai+6Hg uuCim4CGAbzWaG3rrXmbZKQ7RKNZYPgYbYGpXqohFt+jbn47AdI6JhxPwLqcRk2aHgpm 5z09a9+As8Z9pNmnQSDbo3EtEAzhGO3Z/STEfZOUcG80XR/bYqqsSlgo55A5427PqyXU g5kg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=R9lR+T+it4zXhO0VHI513uRYuauDnEwKY8nbzxlXDBk=; b=Mr0NlXb8SxR4akn24Kk+7/fXe4+ZkxJMchwQcNPcq7FXmUKf155noLJHNEyBM+56KD G5At/LGYxxLc62SlUzGlfFjNFVNlvXLBzkymudpnNCiLic7q3qyXphyw6TYTQl9tH39y +YWheuzrcuRx43QLJzRzCJu86EkAU3bPYTGYzXuFLOjy0fiesWAJamyjnsPQnjHtswDF javgxG/jsZDSZtdzcaI6CdNZWxX8ZF7M+Whb4VkMsOvLKNNvZ3selPb+4USNX7LkUr1I 6xRxuZFSNEt3hMz3n30Jfd0cXKvc+L68KIgwdFQtyaGXljZdQqWe/eBpJamfiPgs41aw 8bTA==
X-Gm-Message-State: APjAAAVsnH1akJOckHq20Oyqn43pB5LsCjIhTVWzlFlTDqU2We42EDoP c2D2XbuWgN51zdY4noPg9t4afIFqWyoH6HxvgCJSa6ww
X-Google-Smtp-Source: APXvYqydXwtAcnpRBdOQAy3dLb95vgCxJmWZnysoCYKPh10qPKUTai9uxpAEQzkYW+wUfWsg4B14J01HF8yRysf1EXM=
X-Received: by 2002:ad4:4dce:: with SMTP id cw14mr837681qvb.162.1582823919030; Thu, 27 Feb 2020 09:18:39 -0800 (PST)
MIME-Version: 1.0
References: <CAHzoHbtmJGB8QY==A5EMzzSwh+8bQjhbVgPBjA3kHJGxpCD_zA@mail.gmail.com> <c8828557-85a4-d002-cc8f-a8cd8da0aeaa@cisco.com>
In-Reply-To: <c8828557-85a4-d002-cc8f-a8cd8da0aeaa@cisco.com>
From: Chris Bowers <chrisbowers.ietf@gmail.com>
Date: Thu, 27 Feb 2020 11:15:54 -0600
Message-ID: <CAHzoHbsU-+fUDdr5knmUE87DudCswwF2qGi11SVSSypT2UXKaQ@mail.gmail.com>
To: lsr@ietf.org, SPRING WG List <spring@ietf.org>
Cc: Peter Psenak <ppsenak@cisco.com>
Content-Type: multipart/alternative; boundary="0000000000006f9efa059f91e933"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/f7mbO3djNTPW4z5z7dWdrU8fPVc>
Subject: [Lsr] clarification of locator block and locator node in draft-ietf-spring-srv6-network-programming and draft-ietf-lsr-isis-srv6-extensions
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Feb 2020 17:18:42 -0000

 SPRING and LSR WGs,

I think that we need a much more detailed description of the locator block
and locator node in either draft-ietf-spring-srv6-network-programming or
draft-ietf-lsr-isis-srv6-extensions.  See original email below.

Thanks,
Chris

On Thu, Feb 27, 2020 at 11:08 AM Peter Psenak <ppsenak@cisco.com> wrote:

> Hi Chris,
>
> On 27/02/2020 17:54, Chris Bowers wrote:
> > LSR WG,
> >
> > Section 9 of draft-ietf-lsr-isis-srv6-extensions-05 defines the  SRv6
> > SID Structure Sub-Sub-TLV. In particular, it defines encoding for the
> > locator block length and the locator node length.  The text refers to
> > [I-D.ietf-spring-srv6-network-programming] for the definition of these
> > concepts.
> >
> > As far as I can tell, the only reference to locator block and locator
> > node in draft-ietf-spring-srv6-network-programming-10 is section 3.1
> > which has the following text:
> >
> >     A locator may be represented as B:N where B is the SRv6 SID block
> >     (IPv6 subnet allocated for SRv6 SIDs by the operator) and N is the
> >     identifier of the parent node instantiating the SID.
> >
> > I think that we need a much more detailed description of the locator
> > block and locator node.
>
> sure, but that would be in the
> draft-ietf-spring-srv6-network-programming-10, not in
> draft-ietf-lsr-isis-srv6-extensions, as these are not a protocol
> specific constructs.
>
> thanks,
> Peter
>
> >
> > Thanks,
> >
> > Chris
> >
>
>