The MPLS WG Archive[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index][Thread Index][Author Index][Subject Index] draft-ietf-mpls-tc-mib-06a.txt
>-----Original Message----- >From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com] >Sent: Tuesday, September 30, 2003 3:58 PM >To: 'tnadeau@cisco.com'; Mpls (E-mail) >Cc: arunv@force10networks.com; hans@ipunplugged.com; >jcucchiara@mindspring.com; cheenu@alumni.princeton.edu; >Wijnen, Bert (Bert); 'Joan Cucchiara x302'; 'Kireeti >Kompella'; swallow@cisco.com; loa@pi.se; mrm@riverstone.net; >zinin@psg.com; adrian@olddog.co.uk >Subject: RE: draft-ietf-mpls-tc-mib-06a.txt > > >[ added MPLS WG list !!!!!!!!!!!!!!!!!] > >Inline > >> >> The reason why the multiple fields >> >> were left in place was because someone (Arun >> >> I think) pointed out that you may want to >> >> specify a hop address AND an AS number for >> >> the case where you want to get to a specific >> >> AS *through* a specific HOP. >> >> >> > >> >a TeHopAddress can contain an AS number. >> >So if you have a separate field for AS number what would then >> >be in the TeHopAddress??? And why would you need two addesses >> >to get to one place? SOrry I am confused here >> >> Because a hop can be identified by BOTH an >> AS number and an IP address. Suppose you want to >> choose an AS via a particular interface on an >> LSR? >> >And an IP address on another interface? >Maybe that would mean two entries in the table?? Perhaps, but the example that was given for needing both was the one I gave above. No one has asked for what you suppose above. --Tom > >Bert >> --Tom >
|
|