RE: draft-rabbat-ccamp-carrier-survey-00.txt

["Richard Rabbat" <rabbat@fla.fujitsu.com>]

Hi Adrian,

Thanks for the extensive review and feedback. I'll answer the little issues
here first. Answers to big issues in an email to follow.

> Little issues.
> 
> a.
> 
> It might be nice if the draft file name gave a little more 
> clue about the content of the survey. You might consider 
> draft-rabbat-ccamp-gmpls-mesh-carrier-survey-00.txt

[Richard] I agree. As you can see from the quoted email from IETF, the
longer filename that I asked for was rejected so I had to shorten it.

> -----Original Message-----
> From: Dinara Suleymanova [mailto:dinaras@foretec.com] 
> Sent: Thursday, July 08, 2004 6:46 AM
> To: Richard Rabbat
> Subject: Re: New Internet draft submission
> 
> Too long file name. Please shorten and resubmit.
> 
> At 09:05 PM 7/7/2004, you wrote:
> >Dear IETF draft submission manager,
> >Attached is a copy of a new draft submitted for consideration by the 
> >IETF CCAMP WG.
> >
> >Title: Carrier Survey Results on GMPLS-based Shared-Mesh Transport
> >Restoration Strategies
> >draft-rabbat-ccamp-carrier-survey-sharedmesh-restoration-00.txt

> b. Please try to avoid spurious characters in the text.

[Richard] I can't get bad characters to print here; are there specific
characters that are printing bad? I tested from windows and Unix boxes...
> 
> c.
> 
> Abstract says that a number of GMPLS routing and signaling 
> standards have been completed. I think the RFCs are only at 
> Proposed Standard at the moment.
> 
[Richard] Yes, will update.

> d. Don't think you need section 2
> 
[Richard] Will remove. 

> e.
> 
> Glad that you have a one paragraph definition of "shared mesh 
> restoration" in the survey. Probably good to copy it into the 
> main draft.

[Richard] Sounds good, will do.

> Cheers,
> Adrian
> 
See you in SD,
Richard.