[prev in list] [next in list] [prev in thread] [next in thread]
List: mpls
Subject: [mpls] Clarification/questions on
From: "HUA Michael" <Michael.Hua () alcatel-lucent ! com>
Date: 2008-06-27 17:26:20
Message-ID: A8394F63B6B99D48B0335DF0E54A11BB01BDE4C1 () USDALSMBS01 ! ad3 ! ad ! alcatel ! com
[Download RAW message or body]
--===============0883585526==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01C8D87A.EA116F2F"
This is a multi-part message in MIME format.
Can the authors or someone knowledgeable in the area provide
clarifications for me. Thanks!
1. The proposed bit locations for Bud/Branch node in Downstream mapping
TLV are in conflict with DS Flags (I and N) which are already defined in
RFC4379. Are they just misplaced and should be moved to bit 2 and 3
within the DS Flags?
2. It's not clear on how the proposed P2MP Egress IP address Multipath
information intents to pack multiple IP Addresses. This affects 4-byte
alignment padding. For example, if there are 2 IPv4 addresses, does this
mean that 8 bytes are used with the last 3 bytes of the each address
being zeroed?
0 1 2 3
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Address Type | Egress Address (4 or 16 octets) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| (continued) | :
+-+-+-+-+-+-+-+-+ :
: Further Address Types and Egress Addresses :
: :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
[Attachment #3 (text/html)]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.3314" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=143390215-27062008><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=143390215-27062008><FONT face=Arial size=2>Can the authors or
someone knowledgeable in the area provide clarifications for me.
Thanks!</FONT></SPAN></DIV>
<DIV><SPAN class=143390215-27062008><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=143390215-27062008>
<P><FONT face=Arial><FONT size=2><SPAN class=143390215-27062008>1. </SPAN>The
proposed bit locations for Bud/Branch node in Downstream mapping TLV are in
conflict with DS Flags (I and N) which are already defined in RFC4379.<SPAN
class=143390215-27062008> Are they just misplaced and should be
moved to bit 2 and 3 within the DS Flags?</SPAN></FONT></FONT></P>
<P><FONT face=Arial><FONT size=2><SPAN class=143390215-27062008>2. It's not
clear on how</SPAN> <SPAN class=143390215-27062008>the </SPAN>proposed
P2MP <SPAN class=143390215-27062008>E</SPAN>gress IP address Multipath
information <SPAN class=143390215-27062008>intents to pack multiple IP
Addresses. This affects 4-byte alignment padding. For example, if there are
2 IPv4 addresses, does this mean that 8 bytes are used with the last 3 bytes of
the each address being zeroed?</SPAN></FONT></FONT></P>
<P><FONT size=2><SPAN class=143390215-27062008>
0 \
1 \
2 \
3<BR> 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<BR>
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR> \
| Address Type | Egress Address (4 or 16
octets)
> <BR>
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR> \
| (continued)
> \
> \
> \
>
> <BR>
+-+-+-+-+-+-+-+-+ &nb \
sp;   \
; \
:<BR>
> \
>
Further Address Types and Egress Addresses
> <BR>
> \
> \
> \
> \
>
> <BR>
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+<BR></SPAN></FONT></P>
<P><FONT size=2><SPAN class=143390215-27062008> </P></SPAN></FONT>
<P><FONT size=2><SPAN class=143390215-27062008></SPAN></FONT><FONT size=2><SPAN
class=143390215-27062008> </P></SPAN></FONT></SPAN></DIV></BODY></HTML>
_______________________________________________
mpls mailing list
mpls@ietf.org
https://www.ietf.org/mailman/listinfo/mpls
--===============0883585526==--
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic