Re: [v6tc] v6tc draft charter discussion

Hi Pekka, all,

I don't mind ... actually I was tempted to start some noise yesterday
already, but I wondered if somebody will complain about me ;-)

In principle I think I agree with your 1st two suggestions, but not sure if
it makes sense removing the solution documents, in the sense that those are
to be used as inputs only. We aren't at this time proposing to take them as
WG items or whatever like that, but just to note that there are some
proposals in the table, that of course, could evolve, depending on the
analysis and requirement documents.

Next week we will try to get an update of
draft-palet-v6ops-tun-auto-disc-02.txt

It will be nice if the folks can read it and provide any new inputs !

Regards,
Jordi

> De: Pekka Savola <pekkas@netcore.fi>
> Responder a: v6tc-bounces@ietf.org
> Fecha: Fri, 12 Nov 2004 16:06:54 +0200 (EET)
> Para: v6tc@ietf.org
> Asunto: [v6tc] v6tc draft charter discussion
> 
> Hi,
> 
> (If folks don't mind, I'll try to ensure that the process is moving
> forward until WG chair(s) is appointed or someone else steps up..)
> 
> Find below the v6tc draft charter which was discussed at the meeting.
> I made two changes at this point:
> - shifted the first milestones forward a bit
> - tried to clarify point 1).  Note that this was just meant to say
> that we would find a "rough approach" how to move forward (L2TP, an
> existing tunnel server protocol, ...) -- not that we decide the actual
> solution (detailed proposal) yet.  Does this make sense?
> - I removed the end-point discovery *solution* documents from the
> input document list, because apparently that was causing confusion, as
> people also wanted all the other solutions on that list.
> 
> Comments?  Suggestions? ....?
> 
> I think we should try to get the charter in a reasonable shape within
> a week or so.
> 
> .....
> 
> IPv6 Tunneling Configuration (v6tc) WG
> ======================================
> [...] (On Internet Area)
> 
> Description of Working Group:
> 
> IPv6 Operations working group has identified and documented
> IPv6 transition scenarios where the existing, standardized
> solutions are not sufficient.
> 
> In particular, the solution for scenarios where an IPv6
> connectivity provider is helping the customers to set up a
> tunnel needs to be specified.
> 
> Work has already started in identifying the precise
> goals/requirementsfor the solution.
> 
> The action items for the WG are:
> 
> (1) Based on the input documents, gain rough consensus on at most
>     *one* to-be-standardized approach to fit these goals.
> 
> (2) Work on two components of the solution:
>        a) method to discover the tunnel end-point; and
>        b) the specification of the tunnel set-up protocol.
> 
>     Publish the results on Standards Track.
> 
> (3) Document the goals and tradeoffs of analysis for 2)
>     as Informational RFCs.
> 
> Any other tunneling mechanism or any other activity is out of the scope of
> this very focused WG.
> 
> List of documents to be used as input to the WG:
> 
> http://www.v6ops.euro6ix.net/ietf/draft-suryanarayanan-v6ops-zeroconf-reqs-01.
> txt
> draft-nielsen-v6ops-3GPP-zeroconf-goals-00.txt
> draft-ietf-v6ops-assisted-tunneling-requirements-01.txt
> draft-palet-v6ops-tun-auto-disc-02.txt
> 
> Goals and Milestones:
> 
> Nov 2004 Update the documents on goals/tradeoffs
> Dec 2004 Gain consensus on the rough approach for the solution
> Dec 2004 Get initial individual submissions for solutions
> Feb 2005 Submit the solution as WG I-D
> Jun 2005 WG last call on the solution document
> Aug 2005 Submit the protocol specification to the IESG for Proposed Standard
> Aug 2005 Submit the documents on goals/tradeoffs to the IESG
>         for Informational RFCs
> Sep 2005 Shut down or recharter
> 
> _______________________________________________
> v6tc mailing list
> v6tc@ietf.org
> https://www1.ietf.org/mailman/listinfo/v6tc
> 

**********************************
Madrid 2003 Global IPv6 Summit
Presentations and videos on line at:
http://www.ipv6-es.com

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.

_______________________________________________
v6tc mailing list
v6tc@ietf.org
https://www1.ietf.org/mailman/listinfo/v6tc