Re: Next steps on advancing core IPv6 specifications to full Internet standard

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 18 November 2016 19: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 4DBD6129702; Fri, 18 Nov 2016 11:25:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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_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 xLf4PdZH2EaE; Fri, 18 Nov 2016 11:25:13 -0800 (PST)
Received: from mail-pg0-x234.google.com (mail-pg0-x234.google.com [IPv6:2607:f8b0:400e:c05::234]) (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 5B5871296FD; Fri, 18 Nov 2016 11:25:13 -0800 (PST)
Received: by mail-pg0-x234.google.com with SMTP id p66so105830502pga.2; Fri, 18 Nov 2016 11:25:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=K4Fcl7i2wrtIaA1W9USIIq8w4wQ6YUu97NYvtnYSeg4=; b=ZTM3hky/B7vETCcESxC+q9zoZ3rKpmM8+/3xSo3BxXnaqi6c/Kmom0NbsTVmTrHhJi PiMC6heGtzBJY1hcVLMsdDQK+jjpRqWbPPRq+4Mz2/QuZsYkjVoucAVeD7HvdnxOBr0/ l4CZB4uSqnMOyNlHVEQ2L5z+AtPc6UdCFZwPGaWlDTOkU3rEws/wBBeu0+zJnGSGwJc2 cCw2g362jxHgNuvCWZxmrYj7UFAEeOCqeqpEsXpR+wMmOT7BJcUU32wISpfD3r4JbjWz yWDgqOLpID8b8LNVh7XEn0duGqmdnvYFhOFWye07pW0EauyTwgyRDtzmeIeBYmYIo43B KKpg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=K4Fcl7i2wrtIaA1W9USIIq8w4wQ6YUu97NYvtnYSeg4=; b=ioTV/21szFSBxJFMlEbqVblL7B8apYOiBSGJG2WKpJmAuZA+B864rEbEmim+qT1Yux yZ5E07f8Whilooy5bjm5DUucSOP6uOiNBwpqu9mSZdQ0E8Cx6OT5fnxAAwTR51hXa5A0 1JLMd+ecykTfMG0238LA58fq15EIqDDACFhrgeWoCs/ICwlJB6Iq2ObQ7lXlBep7s8FK +mC8vVmiay7ty5MweQn3hYgk6IAvu9YaxoeCErd+kajSiqIE2lwErrs6jndH8O2fXPlu Sqnv9ijsqdn6Tuu/1p37mhkAeEIBNIa3z2MutOEknNsaZOmym9HUvJacDQmLpbaEuHZX x7fA==
X-Gm-Message-State: AKaTC00oJImGWDTWSo6t6t5V1zREOtarnYHrTpxoiqoic2XI47LRKN8NpKe2+fKs1xhpdw==
X-Received: by 10.98.160.29 with SMTP id r29mr1741859pfe.103.1479497112928; Fri, 18 Nov 2016 11:25:12 -0800 (PST)
Received: from [192.168.178.23] ([118.148.127.150]) by smtp.gmail.com with ESMTPSA id a68sm1671885pgc.31.2016.11.18.11.25.09 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 18 Nov 2016 11:25:12 -0800 (PST)
Subject: Re: Next steps on advancing core IPv6 specifications to full Internet standard
To: Hemant Singh <hemantietf@gmail.com>, Tom Herbert <tom@herbertland.com>
References: <451D4151-B805-4A2E-8BAC-B6627C0B669C@employees.org> <CAJE_bqczRSZYWC3tDLXvxRMzqnV9nDjYjUddyRHtwfpGEXvm5w@mail.gmail.com> <CABdyVt5rhiR6TbvFw8m81R_7Hs3t4APrpdd5W-4U6En4dYq1WQ@mail.gmail.com> <CALx6S35V=wAtSWp0_ksCX2emBZZADY+uiqBLPnyHST_q+vJgig@mail.gmail.com> <CABdyVt4CcrNQQSMnmr-jaDuAup+wkFXdJKqdbp_UfBZSLRQ-Mg@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <03b2b86c-7eab-8ee4-a9b3-fddadc8f367a@gmail.com>
Date: Sat, 19 Nov 2016 08:25:18 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <CABdyVt4CcrNQQSMnmr-jaDuAup+wkFXdJKqdbp_UfBZSLRQ-Mg@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/yHGay5AoabsAUzW5N1jlwYxFLSg>
Cc: stephane.litkowski@orange.com, 6man-chairs@ietf.org, 6man WG <ipv6@ietf.org>, Suresh Krishnan <suresh.krishnan@ericsson.com>, 神明達哉 <jinmei@wide.ad.jp>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
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, 18 Nov 2016 19:25:14 -0000

Hemant,

On 19/11/2016 02:41, Hemant Singh wrote:
> Got it - thanks, Tom.
> 
> Did you see my other email related to both the implementations for SR and
> Inband OAM with mixed nodes?  How do nodes know where to add the OAM data
> or parse the SR encoded data if one vendor's node uses add EH while another
> vendor's node uses encapsulation?    If both implementations continue to
> live, we need means to signal to the network what mode is being used for
> certain protocols.   Some means I see are a new DHCPv6 option, a new
> option/bit in the IPv6 ND RA, a new next_hdr in the IPv6 header, or use
> some bits from the Traffic Class and Flow Label in the IPv6 header.

There are no spare bits in the Traffic Class or the Flow Label.

(To be precise: ECN has two bits and diffserv has 6 bits. And the flow
label bits are not allowed to have semantics of any kind.)

    Brian