IETF Logo Mail Archive

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

Hemant Singh <hemantietf@gmail.com> Fri, 18 November 2016 19:29 UTC

Return-Path: <hemantietf@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 EB20F129739; Fri, 18 Nov 2016 11:29:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 FNJM08AWteXz; Fri, 18 Nov 2016 11:29:13 -0800 (PST)
Received: from mail-oi0-x22b.google.com (mail-oi0-x22b.google.com [IPv6:2607:f8b0:4003:c06::22b]) (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 BB64E129620; Fri, 18 Nov 2016 11:29:13 -0800 (PST)
Received: by mail-oi0-x22b.google.com with SMTP id z62so99409267oiz.1; Fri, 18 Nov 2016 11:29:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=kQ2w7SMUufnAhnzkk/qqofLFWFzBmiT6T2Sq0LaDdOY=; b=rYrKJLCG5RgBYQs98Xs0uK3X0Mn7LeYYrieX8cIDYnRH1CFgb6uvZN9ZSoxJ49KiaZ Rhm6GfKLeSUkywDHqYkJ6BSGPoWn7Yn+szOOhhB3VXv8b4AwXYLRhK5sZ+4WCkalYjgr zH2leRHUQHGgj2TdjjoLP4HdK/Mex9hwt8/WLERUUbJTL9ApF3Z+c4AuveGaRSZ6ymMZ L74Igq1xmSPFuRHewTAP2D31uzD3391Zjyc/cBeswl9+AN26WKb/CsvHLiE11YzdFgir 3vIZkd9ueoI6DjDEdI7uuT5e9Df/VZ4ZVA1i0myuBy/1cTitajkVVyrJ9PnuiEVaiQaC GPoA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=kQ2w7SMUufnAhnzkk/qqofLFWFzBmiT6T2Sq0LaDdOY=; b=d2nadDz99XcumsBWudOcrLKl/2eDL+0ZOWfS9bd4aLeUS8jk3KwldVMkRzmJLY9H86 ErvQdViZ9aDYAukivvHB+mQ3HtSVkgX33WC9dOsMrFO6l2+aeRroW2lFsAlCk6/E+hJ+ k9mSJLX81xe68HMIRGsoF3lW62oUvSmZLLk/xsp5UqT1bai+KtJaCHH+fXJouFvLnqa3 N6my19xzvBuZPb9junubvKK/QUVf3OcbbekHOjdfgELSdPWu+GrVQmxmjdgILXwF3Kr3 JHK8LfEnsEZIsvspzuG/lqUi1NG2R2iynaiGge2Npu5Jhc2Ki3ufVyTnZokFpbfit3ag nv4w==
X-Gm-Message-State: AKaTC01yJxKhf3VzyV+a+R3kCcUywD+uSkHRPgGOFHeM63OKuwaso7/m35TNY+qqnq3iKvtbZdVITeqvveNV6A==
X-Received: by 10.202.204.19 with SMTP id c19mr967434oig.138.1479497353152; Fri, 18 Nov 2016 11:29:13 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.15.33 with HTTP; Fri, 18 Nov 2016 11:29:12 -0800 (PST)
In-Reply-To: <03b2b86c-7eab-8ee4-a9b3-fddadc8f367a@gmail.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> <03b2b86c-7eab-8ee4-a9b3-fddadc8f367a@gmail.com>
From: Hemant Singh <hemantietf@gmail.com>
Date: Fri, 18 Nov 2016 14:29:12 -0500
Message-ID: <CABdyVt6LU4baUjCwiPPk8kXOyS6Ehmyk18cU8PehSqf5m2vhew@mail.gmail.com>
Subject: Re: Next steps on advancing core IPv6 specifications to full Internet standard
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary="001a11352d362e4e8d054198525e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/KzJcFIjOyOOa1WCgrBMVvgNe9_4>
Cc: stephane.litkowski@orange.com, 6man WG <ipv6@ietf.org>, Suresh Krishnan <suresh.krishnan@ericsson.com>, 神明達哉 <jinmei@wide.ad.jp>, 6man-chairs@ietf.org
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:29:18 -0000

Brian,

I totally hear you.   This is why I had given Traffic Class and the Flow
Label as the last option.  My intent was to use such bits of another
purpose in a private network.  I already know of a web-scale operator who
uses the Flow Label for ECMP hashes and ECMP routing.  Recall the 20-bit
hash discussed in v6ops by Google?

Cheers,

Hemant

On Fri, Nov 18, 2016 at 2:25 PM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

>
>
> 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.)
>
>

v2.23.0 | Report a Bug | By Email