Re: We don't seem to be following our processes (Re: Network Programming - Penultimate Segment Popping)
Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 06 December 2019 22:57 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 8D16512010C for <ipv6@ietfa.amsl.com>; Fri, 6 Dec 2019 14:57:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-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 yelkWVIJmbhr for <ipv6@ietfa.amsl.com>; Fri, 6 Dec 2019 14:57:19 -0800 (PST)
Received: from mail-pg1-x531.google.com (mail-pg1-x531.google.com [IPv6:2607:f8b0:4864:20::531]) (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 88064120073 for <ipv6@ietf.org>; Fri, 6 Dec 2019 14:57:19 -0800 (PST)
Received: by mail-pg1-x531.google.com with SMTP id x8so4047686pgk.8 for <ipv6@ietf.org>; Fri, 06 Dec 2019 14:57:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=OBJAkn5T2G5leUTAujSXKNZGppZcujaei7M3JowhThQ=; b=KMSaKWsQjmxGTTnb8R1cYtIYelGFk1Ox5OFgzboKElW8N6mUEPuFwZGjkCPsFsfck0 y8399Jvbjxukn/Dtsv800mDy7AeFb7tCyOm75/k38FTBDXcu/oLhyApBnqMiwg+7VeP/ J/hDGi8lX2HlOtk+H4YfNADDCETqVVGS/GyOCmHzsPBrwhdNfFLpk64NlRx9dCVUTsDa O57Nrp6GZsuIdEVUUMeLAvrvnowuKkYQskoit4TExl4x43b+I/DkxFO3qHv4CifUUyXA T6VYe7xPPFau9SPSSzFuBaICTiVFXheXz070VSoPQK8qzIO3z91hJqB6WHjf6RKgmoJE sNVg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=OBJAkn5T2G5leUTAujSXKNZGppZcujaei7M3JowhThQ=; b=ZtWlLrffnS6uPwvgvWOeV04nlrykP028kXTHj2YSNEFs8tdn36nzBuuLDfY9M177y5 cbs5QVwmFZNdGa4U3Px8ejejxTmLp1hh++X1y3xF24e1lHsyMT7OeN5wPAdemeLMlVUn MqH+qQ3Zzl/cJ+Nh8TKcviv9SLBdmvXZCMyJ3k06SxPvVquyn3cpPttzei2EbYBUrx02 51NcAK/nV8aI6qG+rQn74FIFKdcT0B/DUiWNYCLhUPD5IGpXH5ehCeRBItb86PV7lZQh qceRNJao/v+g5nzh2/x+1Kr2tyjszcGQgVRq4+N0cx182L36M7+LIY093qgcKUFVefAk UwbA==
X-Gm-Message-State: APjAAAVIyUPvVZRMH1H+7G+zJtUnLBZC7/hkITSLzR/NV7Q+OpbPBqNw 1rsQ6gSOXy/l6U5TqXCbZWjlYHTM
X-Google-Smtp-Source: APXvYqynYtZq1k1LWqPE/W6IWr6VYKk+LS3hmwf+tthhx+py2BW8rLOegcRH7+N18F5FfcWECTCHfA==
X-Received: by 2002:a63:190c:: with SMTP id z12mr5723197pgl.1.1575673038574; Fri, 06 Dec 2019 14:57:18 -0800 (PST)
Received: from [192.168.178.30] (228.147.69.111.dynamic.snap.net.nz. [111.69.147.228]) by smtp.gmail.com with ESMTPSA id h68sm18667788pfe.162.2019.12.06.14.57.15 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 06 Dec 2019 14:57:17 -0800 (PST)
Subject: Re: We don't seem to be following our processes (Re: Network Programming - Penultimate Segment Popping)
To: Fernando Gont <fgont@si6networks.com>, ipv6@ietf.org
References: <BN7PR05MB56998A05469327E759B5B671AE5D0@BN7PR05MB5699.namprd05.prod.outlook.com> <3AD3BD11-8C34-41FE-B88F-49A9F2561D78@cisco.com> <BN7PR05MB569946D6AA5C6B78AFC05F6BAE5C0@BN7PR05MB5699.namprd05.prod.outlook.com> <8DEDE597-B7B0-48F5-959E-69757315C2AC@employees.org> <BN7PR05MB56996FFC117F512EEA04AFC8AE5C0@BN7PR05MB5699.namprd05.prod.outlook.com> <4FAB68A3-C533-471D-94D0-3F6EB1F32FC1@employees.org> <1e36a492-5931-02de-cf85-63339522b13a@si6networks.com> <F6DD2C7C-DBBF-4B48-B890-3C86005FB9CF@employees.org> <bb3be82d-8ea7-6c29-ad0a-61b491ee997d@si6networks.com> <8A9BC46E-A018-41C0-BE47-4BABC30EFE79@employees.org> <20191205222740.GA9637@ernw.de> <C7BCB0CF-1CA3-4CA8-9E71-13A013955938@employees.org> <430da027-07a7-42f9-60d0-bbb3f3306222@joelhalpern.com> <7c8494a7-9d3c-bd0e-953e-b6dfbb5c5512@gmail.com> <1e721684-0962-4e75-06dc-242cbae74378@si6networks.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <17b7768e-0a48-61a2-f05a-f6c49ee5f0ff@gmail.com>
Date: Sat, 07 Dec 2019 11:57:15 +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: <1e721684-0962-4e75-06dc-242cbae74378@si6networks.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/uIwX1odPD2fISxutlIbNNOCYDsY>
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: Fri, 06 Dec 2019 22:57:21 -0000
On 07-Dec-19 10:22, Fernando Gont wrote: > On 6/12/19 17:55, Brian E Carpenter wrote: >> Joel, >> >> On 07-Dec-19 04:09, Joel M. Halpern wrote: >>> Ole, there is no IETF accepted definition of "limited domain". >>> There is no IETF rough consensus that it is sensible for us to >>> standardize things for "limtied domains". >> >> That's correct, and that's exactly why the "limited domains" draft >> was submitted to the Independent Stream. It is a fact, documented in >> that draft, that quite a lot of chartered IETF work is directed at >> limited domains. > > I'm not necessarily arguing against your point. But I'd note that, when > it comes to IETF consensus, there's no such a thing as "limited > domains", and IPv6 is IPv6 -- we don't have any concept of "IPv6 for the > capital 'I' Internet" and "Modifications for closed domains". > > IIRC, I did support your document on int-area (?). So it is not that I'm > against the concept of limited domains. Just noting that, as > IETF-conseusns, there's no such a thing. > > That said (and without re-looking at your document right now), there's a > difference between a protocol being effectively employed in a limited > domain (mDNS, if you wish), vs something like this, in which you are > *hoping* that your changes don't leak out of your domain... but in fact > you are not really operating in a limited domain if the src/dst > addresses of packets span past your "limited domain". > > > > >>> While there are standards that are designed for specific deployments, >>> they do not to date use that as an excuse to violate existing RFCs. >> >> I'm not sure that statement is literally 100% correct, because some instances >> may well have passed unnoticed or without controversy. SRH insertion >> has not tried to pass unnoticed, and has become controversial. > > My own impression is that it did try to pass unnoticed. draft-voyer-6man-extension-header-insertion-00, a document that I strongly criticised, came out March 28, 2017 and its first sentence read "The network operator and vendor community has clearly indicated that IPv6 header insertion is useful and required." I *really* think that your impression is wrong. This has been public for almost 3 years now. > Even the latest > rev of the EH insertion draft doesn't even have a reference to RFC8200. Well, the current document editor already said that will be fixed. > And if you've read the initial exchange that triggered all other > comments, an author (?) was kind of trying to educate Ron about the > document not doing eh insertion/removal. > > > > >>> Hence, as far as I can tell, the assertion that SRv6 is for limited >>> domains does not justify or excuse violating RFC 8200. And "I want to >>> save some bytes", while very nice, is not a sufficient reason to violate >>> an approved RFC, must less a Full Standard. >> >> On the other hand, running code in a variety of real and deployed >> products is something that we have a long tradition of documenting forEven the latest rev of the >> informational purposes. RFC1094 or RFC3954 for example. > > Major difference: None of the two protocols you've reference do an > outright violation of an IETF standard --- even less an Internet Standard. That wasn't my point. (If you want an example that does violate an IS, try RFC1631.) My point is that we have often document reality. Regards, Brian
- Network Programming - Penultimate Segment Popping Ron Bonica
- Re: Network Programming - Penultimate Segment Pop… Fernando Gont
- Re: Network Programming - Penultimate Segment Pop… Darren Dukes (ddukes)
- RE: Network Programming - Penultimate Segment Pop… Ron Bonica
- Re: Network Programming - Penultimate Segment Pop… Fernando Gont
- Re: Network Programming - Penultimate Segment Pop… otroan
- RE: Network Programming - Penultimate Segment Pop… Ron Bonica
- Re: Network Programming - Penultimate Segment Pop… otroan
- Re: Network Programming - Penultimate Segment Pop… Fernando Gont
- We don't seem to be following our processes (Re: … Fernando Gont
- Re: We don't seem to be following our processes (… otroan
- Re: We don't seem to be following our processes (… Fernando Gont
- Re: We don't seem to be following our processes (… otroan
- Re: We don't seem to be following our processes (… Tom Herbert
- RE: We don't seem to be following our processes (… Ron Bonica
- Re: We don't seem to be following our processes (… Fernando Gont
- Re: We don't seem to be following our processes (… Enno Rey
- Re: We don't seem to be following our processes (… Enno Rey
- RE: We don't seem to be following our processes (… Ron Bonica
- Re: We don't seem to be following our processes (… Bob Hinden
- Re: We don't seem to be following our processes (… Fernando Gont
- Re: We don't seem to be following our processes (… otroan
- Re: We don't seem to be following our processes (… Joel M. Halpern
- Re: We don't seem to be following our processes (… Sander Steffann
- Re: We don't seem to be following our processes (… Alexandre Petrescu
- Re: We don't seem to be following our processes (… Tom Herbert
- Re: [spring] We don't seem to be following our pr… Robert Raszuk
- Re: [spring] We don't seem to be following our pr… Sander Steffann
- Re: [spring] We don't seem to be following our pr… Robert Raszuk
- Re: We don't seem to be following our processes (… Bob Hinden
- Re: We don't seem to be following our processes (… Fernando Gont
- Re: We don't seem to be following our processes (… Fernando Gont
- Re: We don't seem to be following our processes (… otroan
- Re: We don't seem to be following our processes (… Fernando Gont
- Re: We don't seem to be following our processes (… Tom Herbert
- Re: We don't seem to be following our processes (… otroan
- Re: [spring] We don't seem to be following our pr… Andrew Alston
- Re: We don't seem to be following our processes (… Brian E Carpenter
- Re: [spring] We don't seem to be following our pr… otroan
- RE: [spring] We don't seem to be following our pr… Ron Bonica
- Re: [spring] We don't seem to be following our pr… Andrew Alston
- Re: [spring] We don't seem to be following our pr… otroan
- RE: [spring] We don't seem to be following our pr… Ron Bonica
- Re: We don't seem to be following our processes (… Brian E Carpenter
- Re: [spring] We don't seem to be following our pr… Fernando Gont
- Re: Network Programming - Penultimate Segment Pop… Darren Dukes (ddukes)
- Re: We don't seem to be following our processes (… Fernando Gont
- RE: Network Programming - Penultimate Segment Pop… Ron Bonica
- Re: [spring] We don't seem to be following our pr… Ole Troan
- Re: [spring] We don't seem to be following our pr… Andrew Alston
- Re: [spring] We don't seem to be following our pr… Sander Steffann
- Re: We don't seem to be following our processes (… Brian E Carpenter
- Re: [spring] We don't seem to be following our pr… Fernando Gont
- Re: We don't seem to be following our processes (… Joel M. Halpern
- Re: We don't seem to be following our processes (… Tom Herbert
- Re: We don't seem to be following our processes (… Fernando Gont
- Re: [spring] We don't seem to be following our pr… otroan
- Re: We don't seem to be following our processes (… otroan
- Re: We don't seem to be following our processes (… Brian E Carpenter
- Re: [spring] We don't seem to be following our pr… Brian E Carpenter
- Re: [spring] We don't seem to be following our pr… Fernando Gont
- Re: We don't seem to be following our processes (… Fernando Gont
- Re: We don't seem to be following our processes (… Fernando Gont
- Re: [spring] We don't seem to be following our pr… Fernando Gont
- Re: We don't seem to be following our processes (… Tom Herbert
- Re: We don't seem to be following our processes (… Ole Troan
- Re: We don't seem to be following our processes (… Brian E Carpenter
- Re: [spring] We don't seem to be following our pr… Brian E Carpenter
- Re: We don't seem to be following our processes (… Joel M. Halpern
- Re: We don't seem to be following our processes (… Fernando Gont
- Re: [spring] We don't seem to be following our pr… Fernando Gont
- Re: We don't seem to be following our processes (… Fernando Gont
- Separating issues (was Re: [spring] We don't seem… Suresh Krishnan
- RE: Separating issues (was Re: [spring] We don't … Ketan Talaulikar (ketant)
- Re: We don't seem to be following our processes (… otroan
- Re: We don't seem to be following our processes (… Joel M. Halpern
- Re: We don't seem to be following our processes (… Mark Smith
- Re: We don't seem to be following our processes (… otroan
- Re: We don't seem to be following our processes (… otroan
- Re: [spring] We don't seem to be following our pr… Robert Raszuk
- Re: [spring] We don't seem to be following our pr… Alexandre Petrescu
- Re: Network Programming - Penultimate Segment Pop… Darren Dukes (ddukes)
- Re: We don't seem to be following our processes (… Fernando Gont
- Re: Network Programming - Penultimate Segment Pop… Fernando Gont
- Re: [spring] We don't seem to be following our pr… Darren Dukes (ddukes)
- Re: [spring] We don't seem to be following our pr… Robert Raszuk
- Re: We don't seem to be following our processes (… Tom Herbert
- Re: Network Programming - Penultimate Segment Pop… Tom Herbert
- Re: [spring] Network Programming - Penultimate Se… Robert Raszuk
- Re: [spring] We don't seem to be following our pr… Fernando Gont
- Re: [spring] We don't seem to be following our pr… Fernando Gont
- Re: [spring] We don't seem to be following our pr… Brian E Carpenter
- Re: We don't seem to be following our processes (… Mark Smith
- IPv6 header insertion in a controlled domain otroan
- IPv6 header insertion in a controlled domain otroan
- Re: IPv6 header insertion in a controlled domain Fernando Gont
- Re: IPv6 header insertion in a controlled domain otroan
- Re: IPv6 header insertion in a controlled domain Sander Steffann
- Re: IPv6 header insertion in a controlled domain Gyan Mishra
- Re: IPv6 header insertion in a controlled domain otroan
- Re: IPv6 header insertion in a controlled domain Joel M. Halpern
- Re: IPv6 header insertion in a controlled domain Gyan Mishra
- Re: IPv6 header insertion in a controlled domain otroan
- Re: IPv6 header insertion in a controlled domain Tom Herbert
- Re: IPv6 header insertion in a controlled domain jmh.direct@joelhalpern.com
- Re: IPv6 header insertion in a controlled domain otroan
- Re: IPv6 header insertion in a controlled domain Gyan Mishra
- Re: IPv6 header insertion in a controlled domain Gyan Mishra
- Re: IPv6 header insertion in a controlled domain otroan
- Re: IPv6 header insertion in a controlled domain otroan
- Re: IPv6 header insertion in a controlled domain otroan
- Re: We don't seem to be following our processes (… Alexandre Petrescu
- Re: IPv6 header insertion in a controlled domain Sander Steffann
- Re: IPv6 header insertion in a controlled domain Brian E Carpenter
- Re: IPv6 header insertion in a controlled domain Warren Kumari
- Re: IPv6 header insertion in a controlled domain otroan
- Re: IPv6 header insertion in a controlled domain Gyan Mishra
- RE: We don't seem to be following our processes (… Ron Bonica
- RE: IPv6 header insertion in a controlled domain Ron Bonica
- Re: IPv6 header insertion in a controlled domain Sander Steffann
- Re: IPv6 header insertion in a controlled domain Gyan Mishra
- RE: IPv6 header insertion in a controlled domain Ron Bonica
- Re: IPv6 header insertion in a controlled domain otroan
- RE: [spring] We don't seem to be following our pr… bruno.decraene
- Re: IPv6 header insertion in a controlled domain Fernando Gont
- Re: IPv6 header insertion in a controlled domain Tom Herbert
- Re: IPv6 header insertion in a controlled domain Gyan Mishra
- Re: IPv6 header insertion in a controlled domain Fernando Gont
- RE: IPv6 header insertion in a controlled domain Ron Bonica
- Re: IPv6 header insertion in a controlled domain Gyan Mishra
- Re: IPv6 header insertion in a controlled domain Fernando Gont
- Re: topics to circulate Alexandre Petrescu
- Re: topics to circulate Gyan Mishra
- Re: topics to circulate Erik Kline
- Re: topics to circulate Alexandre Petrescu
- Re: topics to circulate Alexandre Petrescu
- Re: IPv6 header insertion in a controlled domain Alexandre Petrescu
- Re: IPv6 header insertion in a controlled domain Alexandre Petrescu