ifStackTable for the Point-to-Point (P2P) Interface over a LAN Type: Definition and Examples
draft-liu-lsr-p2poverlan-12

(Via drafts-eval@iana.org): IESG/Authors/ISE:

The IANA Functions Operator has completed its review of draft-liu-lsr-p2poverlan-07. If any part of this review is inaccurate, please let us know.

We understand that when this document is sent to us for processing, we will perform two actions.

Specifically, we will replace the current reference for ifType registration p2pOverLan (303), RFC 5309, with a reference to this document in the following locations:

1) in the Interface Types (ifTypes) registry at https://www.iana.org/assignments/smi-numbers

2) in the iana-if-type YANG module at https://www.iana.org/assignments/iana-if-type

This update has been approved by the designated expert for ifTypes.

Thank you,

Amanda Baber
IANA Operations Manager

draft-liu-lsr-p2poverlan has been presented to the ISE for publication
as an Informational RFC on the Independent Stream.

==Purpose==

Some time back, with the approval of the DE for the registry, IANA
assigned 0x303 as the "P2P interface over LAN" ifType.  For lack of a
better reference at the time, RFC 5309 was used, but the DE indicated
that a better and more descriptive reference was really needed.  This
document provides that reference and asks IANA to update the registry
to also point at this document.

==History==

Ideally this document would have come through the IETF, probably the
OPS Area.  But it is a short document, doesn't need the weight of the
IETF, and the registry does not need IETF review. So here we are.

The DE for the registry (Dave Thaler) has been involved in the
discussions, and is supportive.

The document was first brought to the ISE in October, 2021 at version
-03. Since then it has been revised several times to address review
comments.

==Non-IETF Work==

There is some risk that this might be confused with IETF work, but the
code point is already assigned, and the risk seems small.

==Security Considerations==

Defining an additional ifType in the registry does not change the
security model for the YANG models concerned.

==IANA==

The document asks IANA to change the reference for the ifType in two
places. The related registry is "Expert Review".

==Reviews==

As well as reviewing the document himself, the ISE commissioned reviews
from Donald Eastlake and Mike McBride. Dave Thaler also looked at the
document in passing as DE.

The reviews led to a number of updates to fully address the issues
raised.

Details of the reviews can be retrieved on request.

draft-liu-lsr-p2poverlan has been presented to the ISE for publication
as an Informational RFC on the Independent Stream.

==Purpose==

Some time back, with the approval of the DE for the registry, IANA
assigned 0x303 as the "P2P interface over LAN" ifType.  For lack of a
better reference at the time, RFC 5309 was used, but the DE indicated
that a better and more descriptive reference was really needed.  This
document provides that reference and asks IANA to update the registry
to also point at this document.

==History==

Ideally this document would have come through the IETF, probably the
OPS Area.  But it is a short document, doesn't need the weight of the
IETF, and the registry does not need IETF review. So here we are.

The DE for the registry (Dave Thaler) has been involved in the
discussions, and is supportive.

The document was first brought to the ISE in October, 2021 at version
-03. Since then it has been revised several times to address review
comments.

==Non-IETF Work==

There is some risk that this might be confused with IETF work, but the
code point is already assigned, and the risk seems small.

==Security Considerations==

Defining an additional ifType in the registry does not change the
security model for the YANG models concerned.

==IANA==

The document asks IANA to change the reference for the ifType in two
places. The related registry is "Expert Review".

==Reviews==

As well as reviewing the document himself, the ISE commissioned reviews
from Donald Eastlake and Mike McBride. Dave Thaler also looked at the
document in passing.

The reviews led to a number of updates to fully address the issues
raised.

Details of the reviews can be retrieved on request.