Re: Moving forward with the CCAMP charter

[dimitri papadimitriou <[e-mail]>]

hi adrian

i would consider the saturarion document and probably cluster it with 
the set of items on "deployment/advices/BCPs/etc."

there is an item on "OAM Requirements for GMPLS Networks" with a 
lifetime of around 18 months, while it is difficult to have a detailed 
view on them wouldn't be advisable to think upon starting an item mid of 
next year where details (could be info) would be put together

several questions

 >     - ASON Routing solutions
 >       * first version of WG draft
 >       * submit for IESG review

-> does this mean you envision a single document for IS-IS and OSPF 
(note i hope these can be submitted to the IESG by 2Q'06 instead of 
October 2006) also cross-WG review period should be considered

 > Mar 06 First version of WG informational I-D Aligning GMPLS protocols 
across the standards bodies

and

 >     - Aligning GMPLS protocols across the standards bodies
 >       - Information I-D not intended for publication as an RFC
 >       * first version of WG draft

-> what the first sub-bullet implies ? note that i do not see other 
specific milestone(s) for this document while the second sub-bullet 
refers to a WG I-D ?

 > Mar 06 Submit GMPLS routing and signaling interoperability advice I-D 
for IESG review

-> do you have more details on this specific work item

thanks for the hard work,
- dimitri.



Adrian Farrel wrote:
> Hi,
> 
> Please find attached a file that contains:
> 
> - a set of proposed *draft* milestones
> - a discussion of why there are so many milestones
> - a high-level explanation of the work items.
> 
> Note that this looks like a lot of milestones, but please read the text on this issue in the attached file. The bottom line is that this is a product of micro management where I have tried to identify all of the I-Ds that we might produce to cover the referenced work, and where I have placed two (sometimes three) milestones for each I-D.
> 
> This micro-management may be over the top, and represents a full pendulum swing from the previous style of CCAMP milestones, but in the light of the hiatus of the last 12 months, i think this may be beneficial and might achieve rapid forwards movement.
> 
> I would welcome your (constructive!) comments.
> 
> Notes:
> - Why isn't my I-D also cited as input material?
>   No insult intended. The current list is simply there to
>   show the ADs that work is already in progress. All I-Ds
>   will be used as input.      
> - Why isn't my pet topic included?
>   Are you sure it is not there between the lines? This 
>   list of milestones isn't completely proscriptive.
>   
> The objective is to have the WG agreed on the milestones that it wants to commit to by the end of August.
> 
> Thanks,
> Adrian
> 
> 
> ------------------------------------------------------------------------
> 
> CCAMP Working Group - Rechartering Effort
> 
> Below you will find
> - a list of proposed milestones
> - an explanation of why this is a long list
> - overview of proposed drafts and work items
> 
> In reviewing this we should look for:
> - topics that are irrelevant or unwanted by the WG
> - topics that have been left out but are wanted by the WG
> - topics that have been assigned the wrong priority or urgency
> - topics or collections or topics that are sufficiently large
>   to potentially warrant their own working group.
> 
> Proposed New milestones
> -----------------------
> 
> Oct 05 First version WG I-D for Advertising TE Node Capabilities in ISIS and OSPF
> Oct 05 First version WG I-D for Automatic discovery of MPLS-TE mesh membership
> Nov 05 Submit ASON Routing evaluation I-D for IESG review
> Nov 05 First version of WG I-D on path computation implmentation advice
> Nov 05 Cross-WG review of I-D for Advertising TE Node Capabilities in ISIS and OSPF
> Nov 05 First version WG I-D MPLS to GMPLS migration strategies
> Nov 05 First version WG I-D GMPLS coordination of VCAT and LCAS
> Nov 05 First version WG I-D Change of LSP ownership between management and control planes
> Dec 05 First version of WG I-D for ASON Routing solutions
> Dec 05 Submit RSVP-TE extensions for inter-domain signaling I-D for IESG review
> Dec 05 Submit Per-domain path computation signaling I-D for IESG review
> Dec 05 First version WG I-D Requirements for Multi-Layer and Multi-Region Networks
> Dec 05 First version WG I-D for Evaluation of existing protocols for MLN/MRN
> Dec 05 First version WG I-D for Protocol solutions for MLN/MRN
> Jan 06 Submit GMPLS signaling in support of Call Management I-D for IESG review
> Jan 06 Submit GMPLS/ASON lexicography I-D for IESG review
> Jan 06 First version of WG I-D for OSPF-TE/GMPLS MIB module
> Jan 06 First version WG Informational I-D for Analysis of inter-domain issues for disjoint and protected paths
> Jan 06 Submit I-D for Advertising TE Node Capabilities in ISIS and OSPF for IESG review
> Jan 06 First version WG I-D MPLS-GMPLS interworking requirements and solutions
> Jan 06 First version WG I-D GMPLS OAM Requirements
> Jan 06 First version WG I-D Routing and signaling for complex optical constraints
> Feb 06 Submit LSP Stitching I-D for IESG review
> Mar 06 First version of WG informational I-D Aligning GMPLS protocols across the standards bodies
> Mar 06 Submit GMPLS routing and signaling interoperability advice I-D for IESG review
> Mar 06 First version of WG I-D for ISIS-TE/GMPLS MIB module
> Mar 06 First version of WG I-D for additional MIB module to cover RSVP-TE signaling extensions
> Mar 06 Submit I-D for Automatic discovery of MPLS-TE mesh membership for IESG review
> Jun 06 Submit Informational I-D for Analysis of inter-domain issues for disjoint and protected paths for IESG review
> Jun 06 Submit GMPLS coordination of VCAT and LCAS I-D for IESG review
> Jun 06 Submit Change of LSP ownership between management and control planes I-D for IESG review
> Aug 06 Submit path computation implmentation advice I-D for IESG review
> Oct 06 Submit ASON Routing solutions I-D for IESG review
> Oct 06 Submit Requirements for Multi-Layer and Multi-Region Networks I-D for IESG review
> Oct 06 Submit Evaluation of existing protocols for MLN/MRN for IESG review
> Oct 06 Submit MPLS-GMPLS interworking requirements and solutions I-D for IESG review
> Oct 06 Submit MPLS to GMPLS migration strategies I-D for IESG review
> Dec 06 Submit OSPF-TE/GMPLS MIB module for MIB doctor and IESG review
> Dec 06 Submit GMPLS OAM Requirements I-D for IESG review
> Apr 07 Submit ISIS-TE/GMPLS MIB module for MIB doctor and IESG review
> Apr 07 Submit Protocol solutions for MLN/MRN I-D for IESG review
> Oct 07 Submit MIB module for RSVP-TE signaling extensions for MIB doctor and IESG review
> Oct 07 Submit Routing and signaling for complex optical constraints I-D for IESG review
> Oct 07 Recharter or close Working Group
> 
> 
> Why so many milestons?
> ----------------------
> The number of milestones shown in this proposed list far exceeds
> anything I have ever seen in a working group charter. This is
> intentional and while it does indicate a heavy work-load it also
> indicates a higher level of micro-management than is usual within
> working groups. Thus two milestones are presented for each I-D
> (adoption as a WG I-D, and passing to the IESG post-WG-last-call).
> 
> This can be compared with the "normal" charter milestones which
> include a single work-related item that may span several I-Ds and
> refers vaguely only to the "submission" of I-Ds.
> 
> In other words, reviewers of this list should not panic because
> of its length, but should see this as beneficial.
> 
> 
> Explanation of I-Ds and work items
> ----------------------------------
> 
> The following text briefly introduces the work items that are
> represented by the milestones listed above. In this text an
> astrix (*) indicates a milestone to be set.
> 
> The work is divided into several categories according to how
> core it is and how it should be prioritized. Existing drafts
> are referenced to indicate that work is already in progress -
> this is not intended to provide a complete list of existing
> drafts.
> 
>   Completing existing work
>   ========================
> 
>     ASON
>     - ASON Routing evaluation
>       - already have draft-ietf-ccamp-gmpls-ason-routing-eval-01.txt
>       * submit for IESG review
>     - ASON Routing solutions
>       * first version of WG draft
>       * submit for IESG review
>     - GMPLS signaling in support of Call Management
>       - already have draft-ietf-ccamp-gmpls-rsvp-te-ason-04.txt
>       * submit for IESG review
>     - GMPLS/ASON lexicography
>       - already have draft-ietf-ccamp-gmpls-ason-lexicography-03.txt
>       * submit for IESG review
>     - Aligning GMPLS protocols across the standards bodies
>       - Information I-D not intended for publication as an RFC
>       * first version of WG draft
> 
>     Interoperability reports and advice
>     - signaling and routing
>       - already have draft-ietf-ccamp-gmpls-addressing-01.txt
>       * submit for IESG review
>     - path computation
>       * first version of WG draft
>         - based on draft-otani-ccamp-gmpls-cspf-constraints-01.txt
>       * submit for IESG review
> 
>     Additional MIB modules
>     - OSPF-TE
>       * first version of WG draft
>         - based on draft-otani-ccamp-gmpls-ospf-mib-00.txt
>       * submit for IESG review
>     - ISIS-TE
>       * first version of WG draft
>       * submit for IESG review
>     - Signaling
>       - Need "living" MIB module under development to catch
>         the minor protocol extensions that have been made
>         * first version of WG draft
>         * submit for IESG review
> 
>     Inter-domain
>     - LSP Stitching
>       - already have draft-ietf-ccamp-lsp-stitching-01.txt
>       * submit for IESG review
>     - RSVP-TE extensions for interdomain
>       - already have draft-ietf-ccamp-inter-domain-rsvp-te-01.txt
>       * submit for IESG review
>     - Per-domain path computation signaling
>       - already have draft-ietf-ccamp-inter-domain-pd-path-comp-00.txt
>       * submit for IESG review
>     - Analysis of inter-domain issues for disjoint and protected paths
>       - Informational I-D to close off the topic and devolve to PCE
>       * first version of WG draft
>       * submit for IESG review
> 
>   New items already started and within existing charter
>   =====================================================
> 
>     Advertising TE Node Capabilities
>     - ISIS and OSPF in the same I-D
>       * first version of WG draft
>         - based on draft-vasseur-ccamp-te-node-cap-00.txt
>       * review by IGP working groups
>       * submit for IESG review
> 
>     Automatic discovery of MPLS-TE mesh membership
>     - depends on TE Node capabilities I-D
>       * first version of WG draft
>         - based on draft-vasseur-ccamp-automesh-00.txt
>       * submit for IESG review
> 
>     Multi-layer networks (also multi-region networks)
>     - Requirements
>       * first version of WG draft
>         - based on draft-shiomoto-ccamp-gmpls-mrn-reqs-02.txt
>       * submit for IESG review
>     - Evaluation of existing protocols
>       * first version of WG draft
>         - based on draft-leroux-ccamp-gmpls-mrn-eval-01.txt
>       * submit for IESG review
>     - Solutions
>       * first version of WG draft
>         - based on draft-papadimitriou-ccamp-gmpls-mrn-extensions-01.txt
>       * submit for IESG review
> 
>     MPLS-GMPLS interworking requirements and solutions
>       * first version of WG draft
>         - material from draft-oki-ccamp-gmpls-ip-interworking-06.txt
>       * submit for IESG review
> 
>     MPLS to GMPLS migration strategies
>       * Informational I-D first version of WG draft
>         - based on draft-oki-ccamp-gmpls-ip-interworking-06.txt
>         - material from draft-ali-ccamp-gmpls-deployment-augmented-model-00.txt
>       * submit Informational I-D for IESG review
> 
>   Minor items just starting but close to heart of WG
>   ==================================================
> 
>     GMPLS OAM Requirements
>     - Interesting and worthwhile
>       * first version of WG draft
>         - based on immature draft-nadeau-ccamp-gmpls-oam-requirements-00.txt
>       * submit for IESG review
> 
>   Minor items just starting and important becuase of inter-SDO interactions
>   =========================================================================
> 
>     GMPLS coordination of VCAT and LCAS
>     - single requirements and solutions draft almost an applicablity statement
>       * first version of WG draft
>         - based on draft-bernstein-ccamp-gmpls-vcat-lcas-00.txt
>       * submit for IESG review
> 
>     Change of LSP ownership between management and control planes
>     - single requirements and solutions draft defines one bit and a procedure
>       * first version of WG draft
>         - based on draft-caviglia-mp2cpcp2mp-02.txt
>       * submit for IESG review
> 
>   More forward-looking
>   ====================
> 
>     Routing and signaling for complex optical constraints
>       * first version of WG draft
>         - based on draft-ashwood-ccamp-gmpls-constraint-reqts-00.txt
>       * submit for IESG review