[Lsr] Regarding draft-liu-lsr-p2poverlan

"Joel M. Halpern" <jmh@joelhalpern.com> Thu, 08 July 2021 14:00 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C1A83A1C83 for <lsr@ietfa.amsl.com>; Thu, 8 Jul 2021 07:00:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.798
X-Spam-Level:
X-Spam-Status: No, score=-2.798 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 8-YnKr25Q7m0 for <lsr@ietfa.amsl.com>; Thu, 8 Jul 2021 07:00:39 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0615A3A1C80 for <lsr@ietf.org>; Thu, 8 Jul 2021 07:00:38 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 4GLHxf4sYJz1nsjM for <lsr@ietf.org>; Thu, 8 Jul 2021 07:00:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1625752838; bh=pif5hl1GlVAWLlqXP5DirpZ8PlJjIrzLD/+aFYDG8xQ=; h=To:From:Subject:Date:From; b=fzN5I3309DuuXE8pHtf126JNLqlS/y4/ADNY19+zDX4ITBldc4sq6OJPUtJ9czPDJ hLlTTx9xxNfUcg9i12mw3AQJW7iD89XPtFlJwurawhNUModXunG5ttJYz2dEhRhZDI PDNNwDcv01vDIOrXsLhdiDtUHDWZvnjdIB88KYJw=
X-Quarantine-ID: <02o4bHel866h>
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.23.64] (50-233-136-230-static.hfc.comcastbusiness.net [50.233.136.230]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 4GLHxf1LnCz1nsZX for <lsr@ietf.org>; Thu, 8 Jul 2021 07:00:38 -0700 (PDT)
To: "lsr@ietf.org" <lsr@ietf.org>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <4daccf08-5327-433c-bb1c-fa8970aaf1dd@joelhalpern.com>
Date: Thu, 08 Jul 2021 10:00:36 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/cj1RH3a07VePpQDEMW4Fm2tXL9o>
Subject: [Lsr] Regarding draft-liu-lsr-p2poverlan
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Jul 2021 14:00:44 -0000

In earlier emails, we brought 
https://datatracker.ietf.org/doc/html/draft-liu-lsr-p2poverlan-02 to the 
attention of the working group.

This draft was written to provide an explanation of how the 303 ifType 
code point that was assigned at Ericsson's request could be used.  It 
builds on RFC 5309 as that example.  While that is not the only possible 
use for the ifType, it is the obvious one, which is why we brough this 
draft to the attention of the LSR working group.

Note that the code point was not assigned by RFC 5309.  The pointer in 
the IANA entry to 5309 was a simpler (probably too simple) of the 
explanation of "This code point can be used with that thing."  Which is 
why this draft also updates the IANA entry (assuming the draft becomes 
an Informational RFC) to point to the draft.

There were some useful comments about the document on thge list.  We 
have updated the document to address those.

There were also concerns expressed by two participants that the document 
is useless.  Obviously, we would not have written it if we thought it 
was useless :-)

Given that LSR is the most obvious consumer of the ifType code point 
(but not the owner of the registry), we were looking to work with the 
LSR working group to improve and advance this document.

If LSR considers this useless or uninteresting, then we will seek other 
ways of publicly documenting how the ifType code point can be used.

Yours,
Joel