ietf
[Top] [All Lists]

RE: Call for Review of draft-iab-rfc4441rev-04.txt, "The IEEE 802 / IETF Relationship"

2013-06-06 09:22:04
Asking IETF WG chairs to deal with passwords is a bit silly.

Maybe they could be emailed a monthly reminder of their personal subscription 
password on the first of each month.

Lloyd Wood
http://sat-net.com/L.Wood/


________________________________________
From: ietf-bounces(_at_)ietf(_dot_)org [ietf-bounces(_at_)ietf(_dot_)org] On 
Behalf Of Stephen Farrell [stephen(_dot_)farrell(_at_)cs(_dot_)tcd(_dot_)ie]
Sent: 06 June 2013 14:12
To: IAB Chair
Cc: IAB; IETF
Subject: Re: Call for Review of draft-iab-rfc4441rev-04.txt, "The IEEE 802      
/ IETF Relationship"

A couple of minor comments:

- For some unfathomable reason IEEE people seem to call mailing
lists "reflectors" - that might be worth a mention. Section 4
otherwise seems repetitive.

-  3.3.1.4 says: Since it is
   possible to participate in IETF without attending meetings, or even
   joining a mailing list, IETF WG chairs will provide the information
   to anyone who requests it.  However, since IEEE 802 work-in-progress
   is copyrighted, incorporating material into IETF documents or posting
   the username/password on mailing lists or websites is not permitted.

That's a pretty bogus setup. I would think that if IEEE do want to
share some or all drafts with us they could much more easily create
a web page when those drafts are available without access control.
Or we could if they didn't mind. (Or I could do it if there's no "we"
that wants to:-) Asking IETF WG chairs to deal with passwords is a
bit silly. I'm not objecting to this, but am suggesting someone ask
IEEE if they'd like to consider the silliness here and fix it.

S.


On 06/05/2013 07:50 PM, IAB Chair wrote:
This is a call for review of "The IEEE 802 / IETF Relationship"
prior to potential approval as an IAB stream RFC.

The document is available for inspection here:
https://datatracker.ietf.org/doc/draft-iab-rfc4441rev/

The Call for Review will last until 20 June 2013.
Please send comments to iab(_at_)iab(_dot_)org.

On behalf of the IAB,
  Russ Housley
  IAB Chair