The MPLS WG Archive

[=?EUC-KR?B?vcW/673E?= <ysshin@sktelecom.com>]

unsubscribe=20

---

----- Original Message ----- 
Fr=
om : Eric Rosen (erosen@cisco.com)
SendTo : Ina Minei (ina@ju=
niper.net)
CopyTo : mpls@ietf.org
Sent : 2004-10-25 11:=
58:19 PM
Subject : Re: [mpls] Host Address FEC

> I agree with you that to represent a host address, one could use
> an Address Prefix with a /32 prefix. However, one would then have to
> define the error handling for an incorrect length and the procedures t=
hat
> must be applied in case one expects to receive a host address but gets=
 a
> length different than 32. Why not have a FEC that represents a host
> address in this case?=20

The question before us is not whether it would be good to have such a thing,
but whether the Host Address FEC as defined in RFC 3036 is that thing.

According to RFC 3036, if an LSP is associated with a host address FEC, then
a packet  can be assigend  to that LSP  only if the packet's  destination IP
address is the same as the "host address" of the FEC.=20

As I  have endeavored unsuccessfully to  explain, this was  intended for use
when  the egress  PE needed  to  infer from  a packet's  incoming top  label
whether the packet is addressed to the egress PE or not.

I believe  that the MPLS Forum document  in question does not  adhere to the
rules specified in section 2.1 of RFC 3036, and hence is in violation of the
LDP spec.=20

In effect,  they are redefining  the Host Address  FEC to meet  their needs.
The only thing that enables them to  get away with this is the fact that the
Host Address FEC, as defined in RFC 3036, is not used.=20

I don't care  if they use a /32  Address Prefix FEC or if  they define their
own FEC  that always has  a /32  address.  I just  would like to  follow the
proper process here, and I think  the proper process is for them to specify,
in their own documents, the FEC  they want, and then request a codepoint for
it.=20

Given that  the Host Address  FEC as  specified in RFC  3036 is not  used, I
think it must be removed before progression to Draft Standard. =20






=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
mpls mailing list
mpls@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/mpls

=

_______________________________________________
mpls mailing list
mpls@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/mpls