The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2004-Mar> msg00017



[Date Prev][Date Next][Thread Prev][Thread Next]  
  [Date Index][Thread Index][Author Index][Subject Index]

WG last call for draft-ietf-mpls-oam-requirements-02.txt

  • From: "Adrian Farrel" <olddog@clara.co.uk>
  • Date: Mon, 8 Mar 2004 08:46:58 -0000

> At 14:22 04/03/07 +0000, Adrian Farrel wrote:
> >5. 3.10.1 has
> >       (2) At an intermediate LSR, accounting of traffic through
> >           LSPs for each pair of ingress to egress.
> >     This is interesting. If the label stack has just one label then I
> >     guess we can peep inside (if the payload is IP). Is this what
> >     you intended,
>
> No.

I am glad to hear it.

> >  or is this requirement really only limited to
> >     "non-merging" LSPs such as LSP tunnels?
>
> Not limited.
> SP uses merging LSP and need per-lsp basis accounting, they will do it
> over merging LSP.

But downstream of a merge point you cannot tell which ingress the data came from.

Re-reading this, I suspect you mean "incoming segment" or "upstream segment" where you
have written "ingress".

Adrian