Re-, Thanks Jiang Dong, for your comments, I'll discuss with the authors about it.
Cheers, Jacni On 4/18/2012 Wednesday 11:08 AM, Jiang Dong wrote: > HiShishio, > It seems the definition of 6rd MIB is more acceptable than the > extension of IP tunnel MIB according to the Softwire meeting in Paris. > Since the 6rd MIB draft itself is quite clear, a clarification of > using one specific way would be helpful : ) > Regards! > Jiang Dong > 2012-04-18 > *From:* Shishio Tsuchiya <mailto:[email protected]> > *Date:* 2012-03-26 22:19 > *To:* jiangdong345 <mailto:[email protected]> > *CC:* cai.lei3 <mailto:[email protected]>; jacni > <mailto:[email protected]>; softwires <mailto:[email protected]>; > cuiyong <mailto:[email protected]> > *Subject:* Re: [Softwires]Comments about 6rd MIB > Jiang > Thanks for comments. > I will do presentation this draft at Friday,and I will ask which idea > is better to the audience and chairs. > If IP tunnel MIB extended is better than 6rdMIB,so we would update and > define extension of IP tunnel MIB. > 6rd MIB is completely reflecting to 6rd configuration. > http://tools.ietf.org/html/rfc5969#section-7 > "sixRdIpv4MaskLen " is same function as IPv4MaskLen. > IPv4MaskLen The number of high-order bits that are identical > across all CE IPv4 addresses within a given 6rd > domain. For example, if there are no identical > bits, IPv4MaskLen is 0 and the entire CE IPv4 > address is used to create the 6rd delegated > prefix. If there are 8 identical bits (e.g., the > Private IPv4 address range 10.0.0.0/8 is being > used), IPv4MaskLen is equal to 8 and IPv4MaskLen > high-order bits are stripped from the IPv4 > address before constructing the corresponding 6rd > delegated prefix. > Regards, > -Shishio > (2012/03/26 15:59), Jiang Dong wrote: > > Hi,authors of 6rd MIB, > > I get some comments about 6rd MIB draft. > > 1) You mentioned the "tunnelIfXTable" in section 5.2. I think it is > a good idea to extend the tunnel MIB, some scenario cannot be included > in RFC4087, such as point to multi-point tunnel like softwire mesh. > > 2) It seems you miss the conformance part in the definition. > > 3) I'm not quite sure what's the "sixRdIpv4MaskLen " used for, can > you explain it? > > Regards! > > > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- -- > > Jiang Dong > > Tsinghua University > >
_______________________________________________ Softwires mailing list [email protected] https://www.ietf.org/mailman/listinfo/softwires
