Re: [mpls] draft-ietf-mpls-forwarding

[Curtis Villamizar <[e-mail]>]

In message <00ce01cf1de4$45fb9ba0$[e-mail]>
"t.petch" writes:
 
> Curtis
>  
> MP2MP Multipoint to Point ?

Multipoint to multipoint.  Ie: capable of supporting <*,G> though
possibly for a policy constrained value of "*".  Some chips can do it
but I'm not sure what routers can do (whether software supports it)
and if so if anyone deploys MP2MP.  At least some P2MP for
distribution of stuff like video, maybe a lot but I don't know.
Plenty of MP2P since LDP is inherently MP2P.

> I would like the first sentence of the Abstract to start the
> Introduction - otherwise there is no intended audience (and I tend to
> skip Abstracts when I know I am going to be interested in a document).

The intended audience is in the intro later on in Section 1.4 ("Target
Audience").

> And is that second clause for Operators eg
> a basis for operators to evaluate forwarding implementations.

It is meant for both operators and system designers.  System designers
(ie: people working for router vendors that buy off the shelf silicon)
need to pick a forwarding chip long before operators are evaluating.
See Section 1.4.

In the case of forwarding the "implementor" is designing a chip.  The
"system designer" is using it in a product.  The operator is (we hope)
trying to find out what if any bad decisions were made in an
evaluation to determine what effect any shortcomings would have before
deploying and finding out the hard way.

> (more to follow - the I-D is big and my reading is slow:-(

No problem.  Thanks for taking a look.

> Tom Petch

Curtis