Re: [Int-dir] Int-Dir - Review of draft-ietf-softwire-dslite-mib-11

["Yu Fu" <[e-mail]>]

Hi Hui,

 

Thank you for your thorough review for this draft. We have updated the draft based on your comments, please see my reply in line.

 

>>2) In section 6.1.1,  “Because some objects defined in the IP Tunnel MIB are not read-write and read-only, a few new objects are defined in DS- Lite MIB.” What is the “read-write” and “read-only”? If it is a special meaning words in MIB, it need a quotation mark here.

 

[Yu]: We have updated this sentence to “Because some objects defined in the IP Tunnel MIB are not readable”.

 

>>3) In page 8, 

>>“dsliteTunnelAddressType OBJECT-TYPE

>>SYNTAX InetAddressType

>>MAX-ACCESS not-accessible

>>STATUS current

>>DESCRIPTION

>>" This object MUST be set to the value of ipv6(2).

>>It describes the address type of the IPv4-in-IPv6

>>tunnel initiator and endpoint."

>>::= { dsliteTunnelEntry 1 }”

 

>>There’s no scenario requiring ipv6z(4)?  It needs a REFERENCE to RFC 4001 in this object definition.

 

[Yu]: In DS-Lite scenario, there is no requirement for ipv6z(4) as it is defined for non-global IPv6 address.

        We have added the REFFERENCE to RFC 4001.

 

 

>>4) In page 10, DsliteNATBindEntry: I think dsliteNATBindMappingExtAddressType and dsliteNATBindMappingIntAddressType should just be dsliteNATBindMappingAddressType and apply to both. If all address objects in the row are of the same type, you only need one type object.

 

[Yu]:Because the dsliteNATBindMappingExtAddressType is the index of the dsliteNATBindEntry, it can’t merge dsliteNATBindMappingExtAddressType and dsliteNATBindMappingIntAddressType into one.

 

>>5) In page 11, it needs a REFERENCE to RFC 4001 in the definition of dsliteNATBindMappingExtPort.

 

[Yu]: Done.

 

>>6) In page 12, it need some description to describe “endpointIndependent, addressDependent, addressAndPortDependent” in more detail in the DESCRIPTION of dsliteNATBindMappingMapBehavior. 

 The same comments to the “arbitrary, paired” in dsliteMATBindMappingAddressPooling. A REFERENCE is also needed.

 

[Yu]: Done.

 

>>7) In page 14, it needs to define a DEFVAL value for dsliteAFTRAlarmConnectionNumber.

 

[Yu]: Yes, we have added a DEFVAL value into the definition of dsliteAFTRAlarmConnectionNumber.

 

>>8) Whether dsliteStatisticSubscriberIdex is enough or direct to get subscribers' information? 

 

[Yu]: As Natv2SubsicriberIndex defined in NATV2-MIB, “A unique value, greater than zero, for each NAT instance  in the managed system……If a NAT instance is deleted, its assigned index value MUST NOT be assigned to another NAT instance at least until reinitialization of the entity's management system”. The dsliteStatisticSubscriberIdex imported Natv2SubsicriberIndex from the NATV2-MIB,  it is enough to direct to get the subscribers’ information. 

 

>>9) I am not very sure what is dsliteStatisticIpv6Session mean? As for IPv6 traffic, there seems no mapping. 

 

[Yu]: This object is defined to count the normal IPv6 session because DS-Lite can offer both IPv4 and IPv6 connectivity.

 

>>10)Whether there has requirement to support multiple instances in DS-Lite? 

 

[Yu]: Yes, we have defined dsliteNATBindMappingInstanceIndex to support multiple instance. It imported Natv2InstanceIndex defined in NATV2-MIB.

 

Thanks again for your kind review.

 

BR

Yu