Extreme Networks' Ethernet Automatic Protection Switching (EAPS) Version 1
draft-shah-extreme-eaps-03

Date: Tue, 10 Jun 2003 08:30:06 -0400
From: "Paul Nikolich"
Subject: Re: IESG question on Ethernet related to-be-RFC
To: "Erik Nordmark" , p.nikolich@ieee.org, "Tony Jeffree" , "Mike Takefman" , bob.grow@ieee.org
Cc: erik.nordmark@sun.com

Erik,

Via this email, I will ask the chairs of the Working Groups most likely to
be affected by this work (Tony Jeffree 802.1, Bob Grow 802.3 and Mike
Takefman 802.17) to look at the RFC and provide comment to you.  Our next
plenary session is scheduled for the week of July 21st, so it will be a
while before any 'official' feedback can be provided.  In the interim,
perhaps Tony, Bob,  or Mike can provide 'un-official' feedback--I will leave
it up to them.

Tony, Bob, Mike--please review the below referenced document and, if
appropriate, put it on your agenda for discussion in July.  Also, if another
WG in 802 should be included in the review/comment that I missed, please let
me know and I'll give them instructions to review it.

Regards,

--Paul Nikolich
Chairman, IEEE 802

----- Original Message -----
From: "Erik Nordmark"
To:
Cc:
Sent: Monday, June 09, 2003 4:47 PM
Subject: IESG question on Ethernet related to-be-RFC


>
> Paul,
> I'm one of the IETF Area Directors and Russ Housley suggested I contact
you.
>
> The issue is a document which the IESG has on its plate:
> http://www.ietf.org/internet-drafts/draft-shah-extreme-eaps-03.txt
>
> The authors have requested by the RFC editor that this be published as
> an INFORMATIONAL RFC and the RFC editor has asked the IESG whether
> this conflicts with any active work in the IETF.
> Since the document is about "Ethernet protection switching" it
> makes sense for the IESG to ask your advise.
>
> If case you are not aware of the RFC editor and informational document
> it is worth-while for me to mention that the RFC editor routinely
publishes
> informational and experimental RFCs that are unrelated to the
standardization
> activities in the IETF.
> Some of these provide documentation of proprietary solutions, as is
> the case in hand. An older example of such a document is RFC 1761.
>
> Note that the IESG can only provide advise to the RFC editor, which will
> make their independent evaluation.
> But in any case, the IESG is interested in the opinion of IEEE 802
> whether this document would conflict with ongoing standardization
activities.
>
> Sincerely,
>    Erik Nordmark
>

Comments sent to authors:

I think the IPR stuff below should be fixed even though RFC 2026
only makes this a requirement for standards track documents AFAIK.


> INTELLECTUAL PROPERTY
>
>    Extreme Networks Inc. has filed patent applications on and related
>    to the technology described herein.

The better form of IPR notice is in RFC 2026 and it says:
        "The IETF has been notified of intellectual property rights
        claimed in regard to some or all of the specification contained
        in this document.  For more information consult the online list
        of claimed rights."
Adding this and sending an IPR notice to the IETF secretariat
so that it can be recorded in the online list would make sense.

Nits:
>    convergence time is still dependent upon the number of notes in the ring.
s/notes/nodes/

>          Destination MAC Address is always 0x00e02b000004.
>          EtherType is always 0x8100.

Have the above been assigned to Extreme?
Is it desirable to ask IANA to record the Ethertype in http://www.iana.org/assignments/ethernet-numbers ?

> AUTHOR'S ADDRESS:
> in 3

nroff directive?

---