Re: [PWE3] PWE3 Charter Update - **DRAFT Charter v0.1**

["Yaakov Stein" <yaakov_s at rad.com>]

Danny and Sasha, 

I will comment both on the charter and Sasha's comments.

s/Frame Realy/Frame Relay/ and please add TDM to that line.
Also s/pseudo-wire/pseudowire/ (I saw one left).

What does "Switching ... ON the traditional service ..." mean today ?
It obviously should not rule choosing the correct PW at a VPLS ingress
PE
(although not defined in PWE3).
I don't care if it rules out an ECMP mechanism peaking at the first
nibble,
since this is only referenced in PWE3, not defined.
Does it rule out an S-PE choosing a path based on a label chosen by the
T-PE
after looking at the native header ?
Does it rule out a PW protection mechanism that emulates the native
service's mechanism ?

"PWE3 will specify requirements for clock recovery ..."
Actually, TICTOC is specifying requirements. What I think PWE needs to
do
is to support TICTOC efforts on the protocol side.

I agree with Sasha that we should be the design authority for PW over
MPLS issues.
In particular, we should be able to block redefinition of PW
functionality,
such as the popping of the PW label while leaving the tunnel label that
has been proposed.
If this requires another logistics RFC, then we should write one.

Regarding PWE security, the MPLS security document intentionally did not
go into
data plane issues for non-IP clients. This was left for PWE to handle.
(I really should refresh the PWE-security drafts ...)

"Publish requirements and specification for PW load-balancing
mechanisms."
Can we add "inverse multiplexing" to "load balancing" ?
I am writing a draft on this now.

"to support the applications of MPLS to transport networks"
did you mean "the application (no s) of MPLS" ?
If so, perhaps "to support MPLS-based transport networks" ?

Did the group ever agree that P2MP PWs are a good idea ?
I seem to recall that at the mike people agreed that there could be the
need
to transport P2MP services over MPLS, but that it was unsure how this
mapped onto the PWE3 architecture. PWs are emulations of "wires" not
"trees".
It may be a better idea to define a non-IP MPLS client that is not a PW.

Y(J)S
_______________________________________________
pwe3 mailing list
pwe3 at ietf.org
https://www.ietf.org/mailman/listinfo/pwe3