Re: WG adoption for draft-hu-rtgwg-srv6-egress-protection

Greg Mirsky <gregimirsky@gmail.com> Thu, 20 February 2020 19:49 UTC

Return-Path: <gregimirsky@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 188B9120072; Thu, 20 Feb 2020 11:49:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 qk27txvvpith; Thu, 20 Feb 2020 11:49:01 -0800 (PST)
Received: from mail-lj1-x22e.google.com (mail-lj1-x22e.google.com [IPv6:2a00:1450:4864:20::22e]) (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 793C81200C1; Thu, 20 Feb 2020 11:49:01 -0800 (PST)
Received: by mail-lj1-x22e.google.com with SMTP id x14so5459779ljd.13; Thu, 20 Feb 2020 11:49:01 -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=X/I6eUggwHW30wGnBiNLKjvkVqZYv4cVHMilYoyz+pk=; b=VJhMbIOsonYK7AwR/u04w7/bCpHt5BTRyMk7fOM1sOzkaBgb+Cv49nPaDXUr+olXtC zfwR+QrDkpw6c+5M9D1HIDNj+9vw6INEHr+xsvnIUUVlH9gV0owfQbFvu1LoDnPkFxmo 2hR9qsLV/D9uEboj+ik+0RheBV2kxdNlauou4xPoaQfzgSF3ooJSEv8Oeh1RuTQqDJpy QggaW286uhS7hhgCWPVshNonZex08zaC6OmdvJ28pm013SNiSMKjtzQ6M7PurNfDhIRK yDi78xI/yi5Vpwe7nBZB54j3UKBdPJKE8Mg0j6ocSyrnn4P6r87AUK1Uhz9aVaewucBn kDRw==
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=X/I6eUggwHW30wGnBiNLKjvkVqZYv4cVHMilYoyz+pk=; b=AYDI9nw6N3rJ2dV3E9NZOIU9tolLDjfV62rqQ3wPl6UsRgSpy21maEzwKhe6usdDcL /dC4aqOgCPRa3gnF6uYI4pghUc5YRhtSILlkR8O5coePoYeomPCgXecTvZpwNmPreIx5 yQ/gUzOYZuCJP0cRnpIcPD962FksU6TxBBrY5/jDznRojUz1h8Ow9s5zOA1hUl2t0lch hoAEZXUbVlFiizsuYRUoBojt8+FGazGG8K0fPaC8Rwk8EtOosWAZ1YV0hwXdTOtycZmb rzdcjCFLFvDoMmg0LBHqyCysQa6USzCskQRrx+R3fi3jLHOSSJDjkYLCVC274j40sni0 4I5Q==
X-Gm-Message-State: APjAAAUFUa4tF0LTOsMARhA43QeeomkiGJ72zDP/pYLz6zLJaOaM+bq6 kRk3BxznoY9/dIzHfOTe+mG9Pr9qha4ugy6L62w=
X-Google-Smtp-Source: APXvYqzwz8Q3n63hFJnuotSUivQp2/c2F+JuniTLc6r5+/e8b/acyNZ9QAK6+UDaNsQSdRPLt60uuSs8RHBw+qBliWQ=
X-Received: by 2002:a2e:7c08:: with SMTP id x8mr19449341ljc.185.1582228139626; Thu, 20 Feb 2020 11:48:59 -0800 (PST)
MIME-Version: 1.0
References: <57a150fb-e91b-4581-9fc0-781e77c43e59@Spark> <c986b387-e6e8-46a7-8f4a-a3417de3776b@Spark>
In-Reply-To: <c986b387-e6e8-46a7-8f4a-a3417de3776b@Spark>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Thu, 20 Feb 2020 11:48:48 -0800
Message-ID: <CA+RyBmV4s=10NwQMMxW3ahNGh=SZcvKU17GmKHncAGqtuuy=RQ@mail.gmail.com>
Subject: Re: WG adoption for draft-hu-rtgwg-srv6-egress-protection
To: Jeff Tantsura <jefftant.ietf@gmail.com>
Cc: RTGWG <rtgwg@ietf.org>, Routing WG <rtgwg-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000375677059f07320c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtgwg/3Kp6pk4Q46NHyFNfV2KOb7RGX2Q>
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: Thu, 20 Feb 2020 19:49:04 -0000

Dear Authors,
I have got a question about the switchover procedure in the scenario
described in Section 3. As I understand, P1 monitors the path to PE3 using,
for example, BFD. Once it detects the failure, P1 starts using the
pre-computed and pre-signaled path towards PE4. In order to do that, P1
does, as described in the text:

P1 modifies the packet before sending it to PE4.

I've looked for what are these modifications and, as I understand it, think
that it is an update to SRH, P1 appends the Mirror SID A4:1::3 to the
segment list. Is that correct understanding? If it is, I'm not sure that it
is a valid operation for P1? Have we heard from 6man experts about this?
I'd greatly appreciate your clarification on this as this mechanism, in my
understanding of the document, is the foundation of the proposed solution
and without it it may not be feasible.

Regards,
Greg

On Thu, Feb 20, 2020 at 11:02 AM Jeff Tantsura <jefftant.ietf@gmail.com>
wrote:

> Dear RTGWG,
>
> The authors have requested RTGWG to adopt
> draft-hu-rtgwg-srv6-egress-protection as the working group document.
> The draft has received support during IETF106 meeting, authors have
> addressed all the comments received, I expect new version that addresses
> latest comments from Yimin to be uploaded within few days.
>
> Please indicate support or no-support by April 5, 2020.
>
> If you are listed as a document author or contributor please respond to
> this
> email stating of whether or not you are aware of any relevant IPR.
> The response needs to be sent to the RTGWG mailing list. The document will
> not
> advance to the next stage until a response has been received from each
> author and each individual that has contributed to the document.
>
> Cheers,
> Jeff & Chris
> _______________________________________________
> rtgwg mailing list
> rtgwg@ietf.org
> https://www.ietf.org/mailman/listinfo/rtgwg
>