The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2000-Jul> msg00329



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

Consensus on compression - draft-ietf-mpls-hdr-comp-00.txt

  • From: Eric Rosen <erosen@cisco.com>
  • Date: Fri, 21 Jul 2000 14:10:27 -0400
  • cc: Eric Gray <EGray@zaffire.com>, "MPLS Mailing List (E-mail)" <mpls@UU.NET>, "'George Swallow'" <swallow@cisco.com>
  • User-Agent: EMH/1.10.0 WEMI/1.13.2 (Mochimune) FLIM/1.12.1(Nishinokyō) Emacs/20.6 (sparc-sun-solaris2.5.1)MULE/4.0 (HANANOEN)


Lou> The case I was thinking about is were there is an inner label that 
Lou> indicates VPN and an outer label that indicates an egress. 

What makes this  case problematic is that pushing on  these two labels would
be a  function of the Provider Edge  router, which is much  less likely than
the CPE to be separated by a low speed link from the backbone. 

If you  want your  draft to be  considered for  standards track, I  think it
should have  a much clearer statement  of its purpose,  maybe even something
like "not recommended for use on links faster than 9.6Kb", or something like
that.  And  a clear  statement that its  use is  optional.  That way  when a
potential  customer complains that  an implementation  is not  conformant to
standards  because it  doesn't use  single  hop compression  on its  gigabit
ethernet link, one can just refer the customer back to the document itself.