The MPLS WG Archive

[Eric Gray <ewgray@mindspring.com>]

As I recall, the reason for this was that there was
an existing implementation that did it this way.  In
some models of the Universe, no further justification
is required. :-)

--
Eric Gray

Gaitonde Anandprasanna wrote:

> I am sorry to repost this question but i am reallly interested in knowing
> this .
>
> If the question i asked is correct then also let me know if in subsequent
> drafts we can change the format of ERO subobject  (i.e. putting the IPv4
> address at the end of the object.)
>
> Here is my previous mail :-
>
> This question was asked by some person earlier but somehow i did not see
> the answers in the mailing lists. If i have missed the answer then please
> provide pointers to mail archives.
>
> I wanted to know why the format of the IPv4 Prefix is that way:
>
>  RSVP ERO subobject IPv4 address:-
>
>  In RSVP-TE, the format of subobject 1: IPv4 address (4.4.1.1) is
>
> 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
>            Type | Length | IPv4 address
> -----------------------------------------------------------------
>         IPv4 address | Prefix Length | Flags
> ------------------------------------------------------------------
>
> Can somebody explain to me: What is the advantage to split the IPv4
> address in two words? From the
> implementation point of view, it should be much easy to put IPv4 address
> in a single word.
>
> Thanx in advance
>
> Pras