Re: who will edit the draft ?

I'm still willing to edit the draft if we're not
talking about wholesale changes, and we're talking
about a relatively modest amount of time (eg, a 
few months). 

Has a decision been made on wg meeting in MPLS?
I'm hoping that the issues don't require a f2f 
meeting, but it would be good to know one way or
the other.

		Mike

On Wed, 2005-01-19 at 17:24, Shoichi Sakane wrote:
> WG chairs,
> 
> I am also interested in the KINK protocol, and have a experience
> to discuss the specification, to implement it in our team.  And I
> am developping a IKE daemon in the KAME project.  So I can be reviewer
> from the KINK and IPsec point of view.
> 
> There are some comments about the draft in the mailing list.
> Who will collect these comments and will edit the draft ?
> If no one did or will do that, our team is ready to gather them
> and will edit the draft.
> 
> There are some people interested in the protocol.  I think that we
> should have a meeting in order to manage the KINK WG.  I am not sure
> that "manage" is suitable word.  To complete the KINK specification may
> be suitable.  We have two items at least.  One is to make a consensus
> the modification of current draft.  Second is to discuss how to
> manage the WG.  I dont mind that the scale of the meeting is
> a WG meeting, a BoF, a closed meeting or a lunch meeting.
> I want to know who will join the meeting.  Of course I will.
> 
> And we have to make a milestone ASAP.  Here is from "Goals and Milestones"
> in the WG page,
> 
> Done	  	Reach Consensus on requirements document
> Done	  	Meet at San Diego IETF to review drafts
> Jan 01	  	Reach Consensus on base draft protocol
> Feb 01	  	Conduct WG last call on base draft prototol
> Mar 01	  	Begin Interoperability bakeoffs
> Aug 01	  	Document interoperability results.
>                 Make decision to recycle or move forward
> 
> The items would be:
> 
> Feb 14          Submit draft kink-07 with editorial modifications.
> Mar 01          Review the issue of current draft, kink-06.
> Apr 01          Reach Consensus on draft.
> May 01          Resubmit revised draft as Proposed Standard.
> Aug 01   	Begin Interoperability bakeoffs.
> Sep 01   	Document interoperability results.
> 
> If the chair has had the set already, I am sorry for my meddling,
> but at least I have not seen yet.  Thease are just my opinion,
> any comment welcome.  That would be help for the chairs.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iQCVAwUAQe8Os7MsDAj/Eq++AQL92AQAj0kkXCrIouO33S6+3BfbN6bSu+3MmrJN
dMRqgp+aIleFfI9GZFnwyhycgSAixDtBlrM5gl48NvXU3SGOfNlmy3D3iyMXsDIL
eIeiJHG//xuwmWTDEp60l2hvrOvqyUl47QtvAAMHDeLeZp8DhTHwfB4KyP+6ot4E
CfSqcGGTwMg=
=dKxZ
-----END PGP SIGNATURE-----