Re: [spring] We don't seem to be following our processes (Re: Network Programming - Penultimate Segment Popping)

Tom Herbert <> Thu, 05 December 2019 22:03 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 768421201A3 for <>; Thu, 5 Dec 2019 14:03:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ab3MSBF5QgAx for <>; Thu, 5 Dec 2019 14:03:12 -0800 (PST)
Received: from ( [IPv6:2a00:1450:4864:20::52a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id D20D6120168 for <>; Thu, 5 Dec 2019 14:03:11 -0800 (PST)
Received: by with SMTP id cm12so4050020edb.11 for <>; Thu, 05 Dec 2019 14:03:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=wIzv0+iMVfrjNMaBM1eK/F5RK1hShXGawpPL9xcEHNU=; b=XJR3NSDLdtCogmZEfQAOUhy5ePVVJoFQzy2pBDvemNsz+S7alTSlD54uS0zcwruP0b r9SVgmTWP2OTFVherBd0Xm9qMrKTbl7DKdgjA53E9pvGFFccAMcktCajgw3hiYTyU80Z lwudG8aeavabQHbTFQzb9UdhmMjhx9H9CUSltN+l7ZEmyWHsRfZSb4OonVnxxzOYSdvQ ind49Rqkleb8rH5dTty5ZzO2jIaUkmZtJybt+HinEg1GlBr1I+A1tjjxSWkJG91DdANu 3DvbCLuyB7oupRjY2C8I69mwGF85Bf0aLHqzGPqTOkqUiZvbZFFNf8ENNNHuYz1dnzHQ 0RDQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=wIzv0+iMVfrjNMaBM1eK/F5RK1hShXGawpPL9xcEHNU=; b=FgD/d0oG2FtyStXGUs5bw/tW/t4R7+qofx59Y0pFQ2Yh4Pzl5grzSX3T0e3h4NV004 m8QbTmo3f3IsQ1fuAZKN+UzXeRf0lNTdjqD9eh2UDf+fWgPPoSkk10yI0m10CJTnV70Z 6wT/O/nEXgZglP+oUxfBPXIZZqld01NARyZQc39M2ltY/HzaT1N2Y2FQGkObKGgqiibI 3I3B5imZAEmh/rFogkbMFg43Eby8+mfZZEeI7b5WahD4DG25GTqsaSxuwDPoPlRW/Sks j68fUvRFX/NdaymoS0mDTqKtGNJds45UGgedcdlXbbXQ3N8iAY11kuCfCehpbZajXfhH canQ==
X-Gm-Message-State: APjAAAWTs1U8eNCIgxIr6OtE8j392wMgKIJoGB8XwHDnC0dLTTS3MJPD 4fobC7lH6Qj9gSQ+HEsK/cP33Bi3zEf7UmYkNwAE4Q==
X-Google-Smtp-Source: APXvYqx9Op8UnqQtoOe7GXX3T/sERkIL9QasOIYj8FNOBQLNQCMFAYBvMv4ryZhwBCP0Ed0pfSZ2Yx0s3XAu4H3riSY=
X-Received: by 2002:a05:6402:a48:: with SMTP id bt8mr13071382edb.62.1575583390207; Thu, 05 Dec 2019 14:03:10 -0800 (PST)
MIME-Version: 1.0
References: <> <> <> <> <> <> <> <>
In-Reply-To: <>
From: Tom Herbert <>
Date: Thu, 5 Dec 2019 14:02:59 -0800
Message-ID: <>
To: Ole Troan <>
Cc: Fernando Gont <>, SPRING WG <>, 6man <>, "" <>, rtg-ads <>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <>
Subject: Re: [spring] We don't seem to be following our processes (Re: Network Programming - Penultimate Segment Popping)
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Source Packet Routing in NetworkinG \(SPRING\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 05 Dec 2019 22:03:15 -0000

On Thu, Dec 5, 2019 at 1:41 PM <> wrote:
> Fernando,
> >>> Point taken. Could you comment on the current state of WG consensus?
> >>
> >> The working group session in Singapore ended with what appeared to be a view that we should continue work on both documents (Mark's and the Voyer draft).
> >> For the state of the wg consensus, I haven't checked with Bob, but I think he will agree with it being classified as "evolving".
> >
> > I polled you about this decision
> > (, and
> > you never responded.
> Sorry, which decision is that supposed to be?
> > Suresh (INT AD) clarified this one list, here:
> >
> >
> > Suresh noted that there wasn't consensus call, even at the f2f meeting
> > (not to mention that the list was never polled in this respect).
> Right, neither of these two documents are adopted as working group documents. And perhaps a more correct phrasing above would be that "The working group session in Singapore ended with what appeared to be a view that work could continue on both of these documents".

I'm not sure what the outcome to the working group session means in
terms of the process. Basically, we have two documents that almost
directly contradict each other (the EH insertion is bad one was in
fact written in response to the EH insertion is good document). They
both can't be right, and Network programming is still assuming the
outcome that EH insertion/intermediate node removal is correct. So to
continue to work on both documents seems to be akin to punting the
disagreement without clarity on how this will ever be resolved. Also,
I'd point out that the EH insertion document is over a year old and
has already been reviewed, I don't see what new information could be
provided at this point that would change the fundamental arguments
against it.

Can we ask for call for working group adoption call on these?


> > I would say that it seems we have not been following the processes that
> > should be followed. This has happened repeatedly over time, for this
> > very same topic. The process seems to be biased, and thus unfair to the
> > rest of the wg participants.
> Which process are you talking about? Is that documented in an RFC?
> You seem to take it on yourself to represent the "rest of the wg participants", but from my perspective it looks like a few very loud voices.
> Perhaps we should let others speak up, if there is anything more to be said on this topic.
> Ole
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> Administrative Requests:
> --------------------------------------------------------------------