Re: Comments on draft-ietf-rtgwg-srv6-egress-protection

Chris Bowers <chrisbowers.ietf@gmail.com> Tue, 28 July 2020 19:45 UTC

Return-Path: <chrisbowers.ietf@gmail.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 975063A0BCE; Tue, 28 Jul 2020 12:45:13 -0700 (PDT)
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=unavailable 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 spOi4YSCswHr; Tue, 28 Jul 2020 12:45:12 -0700 (PDT)
Received: from mail-ej1-x62c.google.com (mail-ej1-x62c.google.com [IPv6:2a00:1450:4864:20::62c]) (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 2278E3A0AC1; Tue, 28 Jul 2020 12:45:09 -0700 (PDT)
Received: by mail-ej1-x62c.google.com with SMTP id kq25so8910926ejb.3; Tue, 28 Jul 2020 12:45:09 -0700 (PDT)
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=jRjQIVmx/MuPSwXVQjTyES4wanizedPWbc7efXc2gkM=; b=b2QjLQMiLiLr2lsNd0vMrtC02gTlJPOQmJiVx05+duxmJxvMje7YX/9turpjCyl9gS QnYVxMUufqzw7vcJHFom18B462dTDTB/d+xMlW6QpYMnYGqN3lqPALMv3Vt2dz+Ks9xf otvSE2dDdV1y6LGzXh0JNtp3SM3MXN0rGiglgBggvoQj8/2usAsjK9zDvx/LKbbvDcAt 8br7ex5+PNcR35R1z5spOORIdCNZsKVSG9f/ptd6E7I6FednvYRymRzPJDYmNbRDRFZv 5KVs3kEUvEjasyPFGzKCjw5/wB3HzSJ0G8+wgVshne/bXqKEeODlaVK/7UO4R+yPB7Vx n69w==
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=jRjQIVmx/MuPSwXVQjTyES4wanizedPWbc7efXc2gkM=; b=cH6xvFZlqMQDf6pocS1hOBQ6m4Ifc0ynHNvDw2gZL42c+Ik7B13IvczldZq4KNEHZE cD/eBsXBSzYG66y8O3K0Cg4K+r1UeUwWOxRZFKcHSfBgVaJ8WZDXIqkFu6fgXLZv+5ft tzYtA9Wr4BFoBX32mGvnwt1xVBv3S5RR7pviv7q7EfO50r/UzHKdEuvpl8rpykWuYGWT U50DHOl1zCcNPfRB1P54m4QSb0PyyjescxygkpwbSXE+JYg+qMPxSdZZGMR+PPgCe5Tn INYKgpnnO1MEnG1DvmvgOFrBcmGMbwsbZbIxVk1sXAxBKtL9Jk+RqKe1AmES/b754DrN /z8A==
X-Gm-Message-State: AOAM530G/wxMvgjIfwl4PvwM81++uSPyLil9SrhhZQJHQ0IWV2oaC+YX 9usaJfMopHDHc7Cn8Ol1Gb5ywiyyKE13vzDrYa/ScgBo
X-Google-Smtp-Source: ABdhPJz5snSAPdMDciD1NtS6tCfZPlS7Qc2JTUXrmRj+GOl/2DnmYGmgeiBUXrNGtxCXnVRCuJLi4ljyp9umNKOiARI=
X-Received: by 2002:a17:906:cc4d:: with SMTP id mm13mr15267957ejb.191.1595965507479; Tue, 28 Jul 2020 12:45:07 -0700 (PDT)
MIME-Version: 1.0
References: <MW3PR11MB4570EACEE8C80723A0411F31C1720@MW3PR11MB4570.namprd11.prod.outlook.com>
In-Reply-To: <MW3PR11MB4570EACEE8C80723A0411F31C1720@MW3PR11MB4570.namprd11.prod.outlook.com>
From: Chris Bowers <chrisbowers.ietf@gmail.com>
Date: Tue, 28 Jul 2020 14:42:32 -0500
Message-ID: <CAHzoHbtORMa7N6o=nD+2HfPt3-2fovCeK5HvGQSdYy2WQica8w@mail.gmail.com>
Subject: Re: Comments on draft-ietf-rtgwg-srv6-egress-protection
To: "draft-ietf-rtgwg-srv6-egress-protection@ietf.org" <draft-ietf-rtgwg-srv6-egress-protection@ietf.org>
Cc: "rtgwg@ietf.org" <rtgwg@ietf.org>, "Ketan Talaulikar (ketant)" <ketant=40cisco.com@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="00000000000025ab2f05ab85adc9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/yXzVpkCx_dZZ1GYkiQBw7j3Ye88>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtgwg/>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Jul 2020 19:45:14 -0000

I would also suggest that the authors of
draft-ietf-rtgwg-srv6-egress-protection add a reference to Section 5.1 of
RFC8402 (Segment Routing Architecture) which describes the Mirror SID.

Thanks,
Chris


On Mon, Jul 27, 2020 at 10:18 AM Ketan Talaulikar (ketant) <ketant=
40cisco.com@dmarc.ietf.org> wrote:

> Hello,
>
> I am summarizing the questions/comments on the mike on the list with more
> details for a follow-up from the authors.
>
> 1) SRv6 Mirror SID is a new behavior for SRv6 SIDs that needs to be
> formally introduced, defined (using a pseudocode?) and a IANA code-point
> allocated for it. E.g. refer
> https://tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-16#section-4.6
> and for codepoint check
> https://tools.ietf.org/html/draft-ietf-spring-srv6-network-programming-16#section-9.2.
> My question was whether the authors intended to add that in this document
> or a separate Spring document (may be the chairs can guide here)?
> Regardless, this would be something that would require review from the
> Spring WG.
>
> 2) Once (1) has been addressed, then it provides the necessary foundation
> for the review of the IGP encodings for signaling of SRv6 Mirror SIDs
> (Section 4). I would suggest that this proposal then get reviewed in the
> LSR WG - whether in this document or as a separate LSR draft is up to the
> chairs.
>
> Thanks,
> Ketan
>
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg
>