[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: New charter



Kireeti, 

Reply in-lined.

Thanks

Regards... Zafar

<snip>
>
>1) MPLS-GMPLS migration

Yes, .... You may like to rename it as from name it appears that there is a
lot of overlap of this with "7) Deployment considerations for GMPLS". 

>2) GMPLS interoperability issues

Yes, 

>3a) should the IETF take on L1VPNs?

Yes, 

>3b) if yes to 3a, should this be done in CCAMP?

Yes, 

>4) Waveband switching
>5) Control plane work

Yes, but the name is too board, may like to rename it, e.g., Control plane
resiliency and GS. 

>6) Decoder ring for addresses
>7) Deployment considerations for GMPLS

Yes, 

>8) PCE requirements

Yes, 

>9) QoS control
>
>A rough idea of what each of the above entails follows.
>
>1) MPLS-GMPLS migration
>	implementation shift from "MPLS" objects to "GMPLS" objects
>	BCP on deployment migration for the same
>
>2) GMPLS interoperability issues
>	what addresses to use where
>	nits/clarifications of the specs
>	guidelines for path computation & constraints
>	survay
>
>3) L1VPN work items
>	identify protocol extensions needed
>	state what can already be done with what we have
>	do the actual protocol work for requirements that are not met
>	liaisons to SG13 as needed
>
>5) Control plane work
>	resiliency
>	graceful shutdown
>
>6) Decoder ring for addresses
>	for each address field, identify its nature and ITU equivalent
>	(may overlap with part of (2))
>
>
>4, 7-9 are obvious or have been elaborated on the mailing list.
>
>Kireeti.
>-------
>
>PS: The topic of GTTP has carefully been avoided.  More later.
>