Re: [spring] Suggest some text //RE: Request to close the LC and move forward//RE: WGLC - draft-ietf-spring-srv6-network-programming

Bob Hinden <bob.hinden@gmail.com> Fri, 28 February 2020 22:51 UTC

Return-Path: <bob.hinden@gmail.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 D4A703A1F75; Fri, 28 Feb 2020 14:51:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, 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 Dws15uNmFYnN; Fri, 28 Feb 2020 14:51:54 -0800 (PST)
Received: from mail-wr1-x42f.google.com (mail-wr1-x42f.google.com [IPv6:2a00:1450:4864:20::42f]) (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 E92DD3A1F23; Fri, 28 Feb 2020 14:51:53 -0800 (PST)
Received: by mail-wr1-x42f.google.com with SMTP id y17so4957124wrn.6; Fri, 28 Feb 2020 14:51:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=NmUzrrggfB9udvNMRR+0IiRq//yCNRUE6RkJQ+ytdz4=; b=YcL/avNUS+rbvlcQML+Zhy23N5ROxKfxpNMKXko6aVjlV22P03/J0E4Um+Z1Am+uPj YmQh6zyCBzvRTkwjGaZWjj7gKvNGbKyVKrB0Pjb7rVc4q1tEPUAcnL16AzZrimfgXaTO HtkYt1Sek++qCXrmqYN7H54AtnJmUIoOEqGIuyIV/7/2fjAqLiDrjNjj6ic+D5TdnZMd riSMUSPFMN4nmg7HSgtyYXv6hR5/ipLUdwDup9puCLyCKjTCColqsWvtKEWIwzIsszZA MbUIzG17jpqGQu+BbLG21bis9cVjCJQnXkok5aUUA12lJTdUjKtV4jXr9YnkiB/KX4SJ HYew==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=NmUzrrggfB9udvNMRR+0IiRq//yCNRUE6RkJQ+ytdz4=; b=pREq3/3Tc9u3YUm6zKnuWuskMK4NuPEXnAROEiJdZZ5FYGWMYOLI/7kR0AHp9osnbI yNdivpjfnlRfWiqAhctctIJ2DWRyIFEjW5qNoFl4RxWo+/Od0E9lwO9xhsODREBXHaX7 MuqNDWEVVK2uiOegVwieGm4UidVS9BNQVhJ5gsk33P9UMH8G85a0QXjLZLMLaU2nH1J0 0hXsC8xjiC+SPbaH4vuwBn2+HaRVVMDBjbHQyPwzfU75azdRAaBOVf6gLbCbRHFIiU2q sInp/CwBdW1QSqRRO/TkkszU0PWOVXb10kAB2XA07o9o1SDCxsG9IN4LMNzbn9CvBkWE 6yqw==
X-Gm-Message-State: APjAAAWsC/p6VCAYCEGwk8Iqpbv9ppir2ClIC32d7eOnqSWQ486maP9b X5H0aDd3mlGC4kgOIFyEMVg=
X-Google-Smtp-Source: APXvYqxH/Kr1AMqhUlXJ9vA6dQYQCXEIc/4y/kN1DfZmZBexYQc9u5YlNbX33q0p2sP5ScL5R3aSRg==
X-Received: by 2002:adf:fd08:: with SMTP id e8mr1925695wrr.43.1582930312358; Fri, 28 Feb 2020 14:51:52 -0800 (PST)
Received: from ?IPv6:2601:647:5a00:ef0b:41de:3600:7ec8:7d54? ([2601:647:5a00:ef0b:41de:3600:7ec8:7d54]) by smtp.gmail.com with ESMTPSA id z16sm14016675wrp.33.2020.02.28.14.51.49 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 28 Feb 2020 14:51:51 -0800 (PST)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <3F69FA15-F967-44EE-AE1D-600360412BB8@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_BD300E8F-A983-46C4-9633-01D7BC8E7A0E"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Fri, 28 Feb 2020 14:51:45 -0800
In-Reply-To: <2991422b-2de4-f89e-fd79-ada91dc9b3f4@gmail.com>
Cc: Bob Hinden <bob.hinden@gmail.com>, "Xiejingrong (Jingrong)" <xiejingrong@huawei.com>, Ted Lemon <mellon@fugue.com>, "Pablo Camarillo (pcamaril)" <pcamaril@cisco.com>, 神明達哉 <jinmei@wide.ad.jp>, "Joel M. Halpern" <jmh@joelhalpern.com>, "spring@ietf.org" <spring@ietf.org>, "6man@ietf.org" <6man@ietf.org>
To: Brian Carpenter <brian.e.carpenter@gmail.com>
References: <965ff6bbf1cb4c2f8d48b7b535a0cf5b@huawei.com> <2991422b-2de4-f89e-fd79-ada91dc9b3f4@gmail.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/feNmaTlt1F3y4ScM5eC-XmVnmgA>
Subject: Re: [spring] Suggest some text //RE: Request to close the LC and move forward//RE: WGLC - draft-ietf-spring-srv6-network-programming
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: Fri, 28 Feb 2020 22:52:01 -0000

Brian,

> On Feb 28, 2020, at 2:46 PM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
> Hi Jingrong,
> 
> Thanks for your suggestion.
> 
>> so that the tunnel endpoint
>> router (C) doesn't have to deal with SRH.
> 
> Actually, why does this matter? RFC8200 already handles this case:
> 
>   If, while processing a received packet, a node encounters a Routing
>   header with an unrecognized Routing Type value, the required behavior
>   of the node depends on the value of the Segments Left field, as
>   follows:
> 
>      If Segments Left is zero, the node must ignore the Routing header
>      and proceed to process the next header in the packet, whose type
>      is identified by the Next Header field in the Routing header.
> 
> If a non-SRV6 capable router receives SRV6 with segments-left == 0, it
> must ignore it. (So why is PSP needed at all?)

Good point and question.   This is why there is a common base format for all IPv6 routing headers, it allows for this case.

Bob


> 
> Regards
>   Brian
> 
> On 28-Feb-20 20:54, Xiejingrong (Jingrong) wrote:
>> Hi
>> 
>> 
>> 
>> Thanks Ted for the constructive suggestions, which remind me to try to understand the questions. Here are the questions I think give the clear suggestions for LC.
>> 
>> 
>> 
>> Brian: So could the draft make this explicit, because I guarantee you it is not in the least obvious to the non-expert reader?
>> 
>> 
>> 
>> Jinmei: it should say it updates this part of RFC8200 and explain why it's justified.
>> 
>> 
>> 
>> Joel: it would seem that there ought to be a good reason for including PSP, rather than claiming that objectors need to motivate removing it.
>> 
>> 
>> 
>> Bob: There seems to be questions about its relationship with RFC8200.  I am not seeing this as being resolved.
>> 
>> 
>> 
>> As far as I understand the concern and the draft, I may have the following proposed text, though I don’t know if that will help to close or narrow the gap:
>> 
>> 
>> 
>> ****Proposed text to explicitly explain the PSP at the end of 4.16.1 of rev-10****
>> 
>> 
>> 
>> Note that, the SRH is used in an X-in-IP6 tunnel end point case, that is, router (A)
>> 
>> imposes an SRH, and a Penultimate Segment router (B) removes the SRH before
>> 
>> this packet goes to the tunnel end point router (C), so that the tunnel endpoint
>> 
>> router (C) doesn't have to deal with SRH.
>> 
>> 
>> 
>> This has some very important benefits for deployment in some networks when the
>> 
>> final tunnel end point is a lower-end node which is not capable of processing
>> 
>> the SRH for reasons like the hardware is overloaded or unable to upgraded to
>> 
>> process well with SRH.
>> 
>> 
>> 
>> The use of SRH with AH by an SR source node, and processing at a SR Penultimate
>> 
>> segment endpoint node is not defined in <draft-ietf-6man-segment-routing-header>
>> 
>> or in this document.
>> 
>> 
>> 
>> The use of PSP does not impact the MTU Considerations defined in section 5.3 of
>> 
>> <draft-ietf-6man-segment-routing-header>.
>> 
>> 
>> 
>> The design of PSP for the benefits of deployment is based on the understanding
>> 
>> that it does not violate section 4 of RFC8200. In case the RFC8200 text may be
>> 
>> modified in the future, the PSP may also need to change accordingly.
>> 
>> 
>> 
>> In case the final tunnel endpoint router is fully capable of the functionality
>> 
>> of SRH and the SRv6-NP defined in this document, it is recommended not to use
>> 
>> the PSP.
>> 
>> 
>> 
>> ***End****
>> 
>> 
>> 
>> Thanks
>> 
>> Jingrong
>> 
>> 
>> 
>> 
>> 
>> *From:*spring [mailto:spring-bounces@ietf.org] *On Behalf Of *Ted Lemon
>> *Sent:* Friday, February 28, 2020 4:55 AM
>> *To:* Pablo Camarillo (pcamaril) <pcamaril@cisco.com>
>> *Cc:* spring@ietf.org; 6man@ietf.org
>> *Subject:* Re: [spring] Request to close the LC and move forward//RE: WGLC - draft-ietf-spring-srv6-network-programming
>> 
>> 
>> 
>> On Feb 27, 2020, at 3:38 PM, Pablo Camarillo (pcamaril) <pcamaril@cisco.com <mailto:pcamaril@cisco.com>> wrote:
>> 
>>    The discussion that we are having is about PSP which has nothing to do with that.
>> 
>> 
>> 
>> So, there is text in the document that addresses Brian’s question?
>> 
>> 
>> 
>