Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

[802SEC] RE: Draft Liaison to ITU-T SG 15 on COM 15 - R 40 - E


I generally endorse David and Hugh's comments.  A couple other nits.  

1.  We might want to update the URLs to our domain name (e.g.,, 
2.  On page 25, P802.3ae is a completed task force and has been dissolved.  If left, this should be noted.  URL update as above if left.  Your update implied a delete, but didn't make it specific.
3.  Page 42 update EFM item 4.  EFM is now an approved standards project P802.3ah, and therefore a Task Force, not a Study Group.

--Bob Grow

-----Original Message-----
From: Hugh Barrass []
Sent: Wednesday, March 12, 2003 6:02 AM
To: Mike Takefman
Subject: Re: Draft Liaison to ITU-T SG 15 on COM 15 - R 40 - E


I forgot to mention that the "We request that we be given the opportunity to
review..." is an implied offer of work. I think that we should decide who exactly is
going to take on this work before we make the offer.



Mike Takefman wrote:

> Dear SEC and 802.3 Management
> As per procedure 3 (Co-ordination with Other Standards
> Bodies).
> Please find attached the liaison from ITU as well as the
> response crafted by Mike Takefman, Glenn Parsons and
> Hugh Barrass.
> You are requested to review it on wednesday and send
> any comments to Mike Takefman by 9pm whereby they will
> be resolved to the best of my ability.
> Final text will be available on thursday morning so
> that your WGs can review the liaison prior to the
> SEC vote on friday to forward this liaison
> to ITU-T.
> cheers,
> mike
> --
> Michael Takefman    
> Manager of Engineering,       Cisco Systems
> Chair IEEE 802.17 Stds WG
> 2000 Innovation Dr, Ottawa, Canada, K2K 3E8
> voice: 613-254-3399       cell:613-220-6991
>   --------------------------------------------------------------------------------
>                               Name: ITU-T-SG15-reply_02.doc
>    ITU-T-SG15-reply_02.doc    Type: WINWORD File (application/msword)
>                           Encoding: base64
>                 Name: R040e.doc
>    R040e.doc    Type: WINWORD File (application/msword)
>             Encoding: base64