Re: draft-ietf-6man-segment-routing-header-26 violating RFC4291, IPv6 Addressing Architecture?

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 10 March 2020 22:25 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E4103A0404 for <ipv6@ietfa.amsl.com>; Tue, 10 Mar 2020 15:25:25 -0700 (PDT)
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=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 odkNpKhPfW_z for <ipv6@ietfa.amsl.com>; Tue, 10 Mar 2020 15:25:23 -0700 (PDT)
Received: from mail-pl1-x62a.google.com (mail-pl1-x62a.google.com [IPv6:2607:f8b0:4864:20::62a]) (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 AB3143A040E for <ipv6@ietf.org>; Tue, 10 Mar 2020 15:25:23 -0700 (PDT)
Received: by mail-pl1-x62a.google.com with SMTP id g12so101744plo.3 for <ipv6@ietf.org>; Tue, 10 Mar 2020 15:25:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=10tAOY2G/A0M2IzswuBA8eHtxvxmbsYJngUNgCzWItU=; b=TG841OHNNMi8zUEueHxRX8b3Uo6sAknRxFnxXhRNprxKM7T1IUWQJKYzwXWh2Pkg/k NX7EZKWA0Wnd5GtP9bkauut1wjeVytsFF9J9XN6ECmtdw3noGZF9B44Uhw9S4h5DXp2r qJExZEMgG8aeT7T1f1uOem43AcVDg08on9FxCn3cTbD1dKJweaCLYSQxAa2YoIFu8uum K+SEm+vEBPu9D6vC63EWDbCRVpHsbrkCqLlEe7Odq4cMhn9sjIkqlKdxFI3Red5mAbbu I0WYAaTWJgfNqHYF8DLFmeAVTLPk3L5UTBju25hChyCRGSm0YN59utn8mQ78p2DZytfZ DcgQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=10tAOY2G/A0M2IzswuBA8eHtxvxmbsYJngUNgCzWItU=; b=Z27XgFTOMdMuAjuxjCklGjr7F6clwCWaEGaCIlD3gGeScNMpkFS1FCdEANFpzPWkKb 3vKj9gLVqqtWsZWvr1mrbJdsZQz99hvBkehDFQt8gtWYZS25YHij3RFp0jHB74RJH1S0 7TZqKaDEBCaKiWoEOlpbT6wf1GZDvQ+lRXMdk5EwMeZksKQTYZ7ZR4wBqoKFMS/C/kG7 M83k/M2K8rAN9kXO31LbDRCq3Q/yYGAYTWnakMLF24y7QQnEJqj1a9gCkt+ZNSFVfTFa lfQgwUU3h9tDRq31A4SmDKqRejXTFuoAi6U0kk4ollZMHAuMPSG0BbBC/kabQp6krZVy V+3Q==
X-Gm-Message-State: ANhLgQ2c9ESuWEwSlWhFWvVZDdoeYdYP1dpzasFvbEjQSuCkqY3e0Kv9 xSAirYIq8N4FzK1Z9RbT6OOCNXR1
X-Google-Smtp-Source: ADFU+vvToRS8+lALMRsBj39HfqWe7RPUgMKLrHsuF24xouSTtLL2OHnrf7JJGy6vsPRtW2AiFC/3Ag==
X-Received: by 2002:a17:902:9a4c:: with SMTP id x12mr102420plv.297.1583879122760; Tue, 10 Mar 2020 15:25:22 -0700 (PDT)
Received: from [130.216.37.131] (sc-cs-567-laptop.uoa.auckland.ac.nz. [130.216.37.131]) by smtp.gmail.com with ESMTPSA id b18sm49896941pfd.63.2020.03.10.15.25.20 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 10 Mar 2020 15:25:22 -0700 (PDT)
Subject: Re: draft-ietf-6man-segment-routing-header-26 violating RFC4291, IPv6 Addressing Architecture?
To: "Darren Dukes (ddukes)" <ddukes=40cisco.com@dmarc.ietf.org>, Andrew Alston <Andrew.Alston@liquidtelecom.com>
Cc: 6man WG <ipv6@ietf.org>
References: <CAO42Z2xKWYB4F5Fd735E8xTL+KLZBVO73FjKyVqj8fy2uJkNsg@mail.gmail.com> <226A1DDB-2BF9-4F55-81A0-277E4FBB352A@cisco.com> <DBBPR03MB54157EAC694BA9C88340C686EEFE0@DBBPR03MB5415.eurprd03.prod.outlook.com> <4A42505B-7D4C-43F7-B8DA-3F3CA60C44D4@cisco.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <9a67bfcf-686f-d2cf-5da7-190c28f60a9e@gmail.com>
Date: Wed, 11 Mar 2020 11:25:18 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <4A42505B-7D4C-43F7-B8DA-3F3CA60C44D4@cisco.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/ILRpTdgliTDvqMc9mNknoWyRS1A>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Mar 2020 22:25:26 -0000

Darren,

Does that ticket mean that the issue was fixed in version -14 or version -15? I can't see anything in the diffs for those versions that relates to RFC4291, and it isn't in the references.

In any case, I don't think the target for this issue should be the 6MAN document. It should be RFC8402, which says:
   An instruction is
   associated with a segment and encoded as an IPv6 address.
This train left the station when RFC8402 was approved.

Regards
   Brian Carpenter

On 11-Mar-20 05:06, Darren Dukes (ddukes) wrote:
> Hi Andrew please see issue #66 for the closure record.
> 
> https://trac.ietf.org/trac/6man/ticket/66
> 
> Darren
> 
>> On Mar 9, 2020, at 3:18 PM, Andrew Alston <Andrew.Alston@liquidtelecom.com <mailto:Andrew.Alston@liquidtelecom.com>> wrote:
>>
>> Hi Darren
>>
>> >  Hi Mark, the working group discussed the
>>  > association with RFC4291 and closed it with
>>  > the text in the document.
>>
>> Can we get a reference to these discussions please - would just be useful to back and refresh memories and wasn’t able to find them
>>
>> Thanks
>>
>> Andrew
>>
>>
>>
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>