[ieee-ietf-coord] Fwd: Upcoming request for EtherType allocation

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Wed, 07 November 2018 01:13 UTC

Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ieee-ietf-coord@ietfa.amsl.com
Delivered-To: ieee-ietf-coord@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37D4A1277BB for <ieee-ietf-coord@ietfa.amsl.com>; Tue, 6 Nov 2018 17:13:22 -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, HTML_MESSAGE=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 nvSGO-4H27bT for <ieee-ietf-coord@ietfa.amsl.com>; Tue, 6 Nov 2018 17:13:19 -0800 (PST)
Received: from mail-lj1-x230.google.com (mail-lj1-x230.google.com [IPv6:2a00:1450:4864:20::230]) (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 A487112870E for <ieee-ietf-coord@ietf.org>; Tue, 6 Nov 2018 17:13:19 -0800 (PST)
Received: by mail-lj1-x230.google.com with SMTP id v15-v6so4622198ljh.13 for <ieee-ietf-coord@ietf.org>; Tue, 06 Nov 2018 17:13:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=Cgrm/qBwsp+dIF3q0Ifiqfvw0Jb83vS7hZMEuKb7P2Q=; b=XGqQTmI0Yg6khh3WYg8sPBE+Ods+nook4Fml/kvAsGx95q1wis6qc+yg0pfHOKkzAd 9flgfb3Dy1Xt6GzpZho1Zl+fNkKAoXXIhx2V/TebtsfANOAM3UsR2b30JJkOsUuOpV8r R7Gls/2G7+Uj26b3OMpmeVH7uPNhFEs7qoS1N4u5pniG0xYr7rE8S5thhJMgWFAI91sW H7IjDmP1wr6pC5pbwpLx+3gwMv3W8KfJObRB1Q8Th+9KCN+7MqlUjnJ6/gjwQeO8n31x l0P1jIGipSuuQSb0vfnUPPrNfFm/1ncs/zkYjXdwOP3GfoPYZ2KxeMI/Kfx3E/EHqOex 2Tbw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=Cgrm/qBwsp+dIF3q0Ifiqfvw0Jb83vS7hZMEuKb7P2Q=; b=r9Bos8eO8fzsSzCLFTIgTqptx9IGgf1+Za4yxrhytaAAD7tZ0xf0pc8juxOcR3UVJr X1lOjI3UYEb7MY/gNilbE18bOnMdbnf08gBCCUfLrt4FJqSR5W+it2TvACejcdUeyBl9 6/6OHcUwKYwN39Sq5LQPT63sTnYcYSzKbr5FU6BiLjOsxMLwnyeBYylaiN/CTPi++/s6 qGWHi+TCTE6umRhkg0vexmnrbNjPp70A3JITiZhO5cIH/oaUDxPWN6mda2yxIaTulFfa 28Rh9JPpM4ePA4g3WVWoBkp891LF5wol7Hb1uYjcgRSBSYU5NQYFHPvsz1oFY+ebXhN1 Jz2A==
X-Gm-Message-State: AGRZ1gICDH+yR7aX19QqNI6lb4AtBuysSrRaNntyYQf1cf4nQSjVPNMw lx9bdA4WF5IfkV4Snzn2nV/1SKbvHl6KDcljbTn0l0od
X-Google-Smtp-Source: AJdET5erC3/Cnu0oe+fRGjhNtJQKjgYlulaNWYMjseSsNZRaWlIgDsQtzGo1nHjerbX9UG/E9sTrk7QKh0glPOqP/6k=
X-Received: by 2002:a2e:9dd0:: with SMTP id x16-v6mr9671806ljj.164.1541553197192; Tue, 06 Nov 2018 17:13:17 -0800 (PST)
MIME-Version: 1.0
References: <09C43D84-A5CC-4400-9FDD-814E33D2B3AC@cisco.com>
In-Reply-To: <09C43D84-A5CC-4400-9FDD-814E33D2B3AC@cisco.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Wed, 7 Nov 2018 08:13:07 +0700
Message-ID: <CAKKJt-dVH7t-Yfn-4FAQjq6=fnwqhUeikrHZinrDduApVj2R-w@mail.gmail.com>
To: "<ieee-ietf-coord@ietf.org>" <ieee-ietf-coord@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b89948057a08d2a2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ieee-ietf-coord/R2wv1gOx--O4xBj8aT1w-fq8e-o>
Subject: [ieee-ietf-coord] Fwd: Upcoming request for EtherType allocation
X-BeenThere: ieee-ietf-coord@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Management-level discussions between IEEE and IETF on topics of interest to both SDOs <ieee-ietf-coord.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ieee-ietf-coord>, <mailto:ieee-ietf-coord-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ieee-ietf-coord/>
List-Post: <mailto:ieee-ietf-coord@ietf.org>
List-Help: <mailto:ieee-ietf-coord-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ieee-ietf-coord>, <mailto:ieee-ietf-coord-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Nov 2018 01:13:22 -0000

Dear IEEE 802/IETF Folk,

The IPPM working group has been talking to the RAC privately about an
EtherType request, and I told them I'd let the coordinators know, since
we're meeting on Friday and if anything pops up (like, "oh, we just ran out
of EtherTypes" - I am kidding) everyone would know earlier.

Details follow. Mirja is now the responsible AD for IPPM, and is on this
coordination team, so the right thing will happen..

Spencer

---------- Forwarded message ---------
From: Brian Weis (bew) <bew@cisco.com>
Date: Tue, Nov 6, 2018 at 5:17 PM
Subject: Upcoming request for EtherType allocation
To: spencerdawkins.ietf@gmail.com <spencerdawkins.ietf@gmail.com>
Cc: ippm@ietf.org <ippm@ietf.org>


Hi Spencer,

As discussed in today’s IPPM WG meeting, we are expecting in the future to
request publication of an Internet-Draft that requires a new EtherType to
to be allocated. You mentioned that this might be an interesting topic for
this week’s IETF/IEEE 802 meeting, and so I’m passing on the following
notes.

We would request an EtherType for it "In-situ OAM (IOAM)” (see
https://tools.ietf.org/html/draft-weis-ippm-ioam-eth-00). We understand
that there is a process for IANA to request this from the IEEE 802, and
have put this into our IANA Considerations section.  Additionally, we had
an early private exchange with some members of the IEEE 802 RAC (the entity
that performs the allocation), who gave advice to make sure we only ask for
one EtherType of this purpose, and we’ve followed that advice. I don’t
expect any issues with defining the EtherType we need, but if you’d like to
check with them that would be great.

Thanks,
Brian