Re: [Lsr] Fwd: I-D Action: draft-liu-lsr-p2poverlan-00.txt

"Joel M. Halpern" <jmh@joelhalpern.com> Fri, 18 June 2021 15:29 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 929D33A1515 for <lsr@ietfa.amsl.com>; Fri, 18 Jun 2021 08:29:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.799
X-Spam-Level:
X-Spam-Status: No, score=-2.799 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, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=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 gTyAuk9SnUn1 for <lsr@ietfa.amsl.com>; Fri, 18 Jun 2021 08:29:07 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (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 1A10D3A1511 for <lsr@ietf.org>; Fri, 18 Jun 2021 08:29:07 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 4G62ry5hJlz6G91f; Fri, 18 Jun 2021 08:29:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1624030146; bh=tsLyqTn3HGGy3whfhpkKpVUocGVxcrq6D9VXzCTRmDk=; h=Subject:To:References:From:Date:In-Reply-To:From; b=RxFmCEw35LryPn5wLzCiNPhPBTJe30VzZHlhInER7zNZgiJWdLmeaKRg+FO2GBP/+ VR0yfXI3v6x58GLu7sd/zYjVvA01BJweQhimGU7GnXmJFaXSCfebwWphiG41JZfKzr Uxz41nzERY2ns691dZ46RifpWpVX3ObCRVlvNReI=
X-Quarantine-ID: <QG18bjUYWeBl>
X-Virus-Scanned: Debian amavisd-new at a2.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 maila2.tigertech.net (Postfix) with ESMTPSA id 4G62rx72Hzz6G8Mf; Fri, 18 Jun 2021 08:29:05 -0700 (PDT)
To: tom petch <ietfc@btconnect.com>, "lsr@ietf.org" <lsr@ietf.org>
References: <162385200442.4672.15557284720360290794@ietfa.amsl.com> <782ee34f-2e88-d820-18f8-baacf01610fc@joelhalpern.com> <DF0C4D45-DF81-446A-8CCE-97B44747AC20@cisco.com> <2d5f0af6-7849-9b71-68f5-5da8b175e3df@joelhalpern.com> <AM7PR07MB6248048C239222E658D9BC72A00D9@AM7PR07MB6248.eurprd07.prod.outlook.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <332a4b21-1cb3-cfa5-b7fd-d50c3abd053a@joelhalpern.com>
Date: Fri, 18 Jun 2021 11:29:04 -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
In-Reply-To: <AM7PR07MB6248048C239222E658D9BC72A00D9@AM7PR07MB6248.eurprd07.prod.outlook.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/-ODAfnCncI0esNzXwqqRm9SH48o>
Subject: Re: [Lsr] Fwd: I-D Action: draft-liu-lsr-p2poverlan-00.txt
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: Fri, 18 Jun 2021 15:29:12 -0000

Tom, I am not sure what you mean by "the update has happened">  The code 
point has been assigned.  Assuming this document becomes an RFC, it will 
be significantly clearer if the 303 code point IANA entry points at this 
for information instead of 5309.  So this document requests that update.

Yours,
Joel

On 6/18/2021 7:47 AM, tom petch wrote:
> From: Lsr <lsr-bounces@ietf.org> on behalf of Joel M. Halpern <jmh@joelhalpern.com>
> Sent: 16 June 2021 21:46
> 
> This document (and the code point) are intended to be in line with 5309.
>    I believe they are.  If we got it wrong, please help us fix it.
> 
> A reference would be reasonable to add.  (The IANA entry for the code
> point does reference 5309.)
> 
> <tp>
> which confused me as RFC5309 has no IANA considerations and no reference to 303.  I understand how this is so but think that this I-D could explain this.  I think that the I-D is wrong to ask IANA to perform an update - the update has happened.
> 
> What would help would be for this I-D to explain that the allocation was made by Expert Review and to ask that IANA update the reference to point to this I-D and then this I-D can point back to RFC5309.  This is almost an updates to 5309 as it give a value to the specification - I can see the IESG having fun with that concept but I would go for it.
> 
> I think too that this I-D should reference and build on RFC5309.  At present it looks like an Unused Ref.
> 
> Tom Petch
> 
> 
> 
> Thank you,
> Joel
> 
> 
> 
> On 6/16/2021 4:41 PM, Acee Lindem (acee) wrote:
>> Hi Joel,
>>
>> At first I wondered where this document should reside and then decided that LSR is probably as good as any other place.
>>
>> Can you guys check whether it is mostly in line with https://datatracker.ietf.org/doc/rfc5309/ and comment as to whether it should be referenced?
>>
>> Thanks,
>> Acee
>>
>>
>> On 6/16/21, 11:10 AM, "Lsr on behalf of Joel M. Halpern" <lsr-bounces@ietf.org on behalf of jmh@joelhalpern.com> wrote:
>>
>>       Recently, Ericsson requested and received an IF Type assignment from
>>       IANA (with expert review) for point-to-point over Ethernet links.
>>
>>       It was noted during the discussion around the assignment that a document
>>       (eventually, we hope, an RFC) describing how to use that and why we
>>       asked for it would be helpful.
>>
>>       The below announcement is that draft.  We would like to work with the
>>       community to improve and clarify teh draft.
>>
>>       Thank you,
>>       Joel
>>
>>
>>       -------- Forwarded Message --------
>>       Subject: I-D Action: draft-liu-lsr-p2poverlan-00.txt
>>       Date: Wed, 16 Jun 2021 07:00:04 -0700
>>       From: internet-drafts@ietf.org
>>       Reply-To: internet-drafts@ietf.org
>>       To: i-d-announce@ietf.org
>>
>>
>>       A New Internet-Draft is available from the on-line Internet-Drafts
>>       directories.
>>
>>
>>                Title           : Interface Stack Table Definition for Point to
>>       Point (P2P) Interface over LAN
>>                Authors         : Daiying Liu
>>                                  Joel Halpern
>>                                  Congjie Zhang
>>        Filename        : draft-liu-lsr-p2poverlan-00.txt
>>        Pages           : 7
>>        Date            : 2021-06-16
>>
>>       Abstract:
>>           The point-to-point circuit type is one of the mainly used circuit
>>           types in link state routing protocol.  It is important to identify
>>           the correct circuit type when forming adjacencies, flooding link
>>           state database packets, and monitor the link state.  This document
>>           defines point-to-point interface type and relevant stack tables to
>>           provide benefit for operation, maintenance and statistics.
>>
>>
>>       The IETF datatracker status page for this draft is:
>>       https://datatracker.ietf.org/doc/draft-liu-lsr-p2poverlan/
>>
>>       There is also an htmlized version available at:
>>       https://datatracker.ietf.org/doc/html/draft-liu-lsr-p2poverlan-00
>>
>>
>>       Internet-Drafts are also available by anonymous FTP at:
>>       ftp://ftp.ietf.org/internet-drafts/
>>
>>
>>       _______________________________________________
>>       I-D-Announce mailing list
>>       I-D-Announce@ietf.org
>>       https://www.ietf.org/mailman/listinfo/i-d-announce
>>       Internet-Draft directories: http://www.ietf.org/shadow.html
>>       or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>
>>       _______________________________________________
>>       Lsr mailing list
>>       Lsr@ietf.org
>>       https://www.ietf.org/mailman/listinfo/lsr
>>
> 
> _______________________________________________
> Lsr mailing list
> Lsr@ietf.org
> https://www.ietf.org/mailman/listinfo/lsr
>