Mobile IPv6 Mobile IPv6 Connectathon 2003 2003 Connectathon - - PowerPoint PPT Presentation

Connectathon Connectathon 2003 2003 Interoperability Testing Report Interoperability Testing Report Samita Chakrabarti Samita Chakrabarti Samita Samita. .chakrabarti chakrabarti@Sun.com @Sun.com

Mobile IPv6 Mobile IPv6

IETF56 IETF56

2 IETF56 March 17, 2003

Connectathon Connectathon 2003 ( 2003 (March 2

March 2 – – 6 6)

)

Implementation/Test Participants Implementation/Test Participants Cisco Cisco HP HP-

• True64

True64 HP HP-

• UX

UX University Of Helsinki University Of Helsinki KEIO University KEIO University NEC NEC Nokia Nokia Samsung Samsung Network Associates(Analyzer) Network Associates(Analyzer) TAHI (Conformance Tests for ID TAHI (Conformance Tests for ID-

• 20 and ID

20 and ID-

• 19)

19) UNH (Interoperability Tests) UNH (Interoperability Tests) Sun (Technology Co Sun (Technology Co-

• ordination)
• rdination)

3 IETF56 March 17, 2003

Connectathon Connectathon ad ad-

• hoc testing topology

hoc testing topology

MN MN HA HA CN CN MN MN R R

Cthon Cthon subnet subnet

Private Test subnet Private Test subnet MIPv6 Test MIPv6 Test Subnet Subnet

Each booth had 3 drops Each booth had 3 drops

4 IETF56 March 17, 2003

Connectathon2003: Implementations Connectathon2003: Implementations

HA 7 HA 7 implementations

implementations

CN 7 CN 7 implementations

implementations

MN 6 MN 6 implementations

implementations 1 MIPv6 Network 1 MIPv6 Network Analyzer Analyzer implementation implementation More breakdown on a particular implementation functionality More breakdown on a particular implementation functionality:

:

HA HA-

• CN

CN-

• MN

MN

3 3

HA HA-

• CN

CN

2 2

MN MN-

• CN

CN

3 ( 3 (ALL

ALL MNs MNs performed Route performed Route Optimization Optimization) ) HA (only) HA (only) 2

2

5 IETF56 March 17, 2003

Connectathon2003: Drafts Connectathon2003: Drafts

All implementations supported All implementations supported

Draft Draft-

• ietf

ietf-

• mobileip

mobileip-

• ipv6

ipv6-

• 20.txt

20.txt ( (TAHI Conformance and UNH Interoperability Tests TAHI Conformance and UNH Interoperability Tests were performed on them were performed on them ) ) 2 implementations supported : 2 implementations supported : draft draft-

• ietf

ietf-

• mobileip

mobileip-

• mipv6

mipv6-

• ha

ha-

• ipsec

ipsec draft draft ( ( No TAHI conformance or UNH Interoperability tests No TAHI conformance or UNH Interoperability tests were performed on HA were performed on HA-

• MN

MN IPSec IPSec features features) )

6 IETF56 March 17, 2003

Connectathon2003: Connectathon2003: MIPv6 Internet Testing

MIPv6 Internet Testing

The The Connectathon Connectathon Consensus Consensus ☺ ☺

• MIPv6 Internet Testing would be beneficial between major

MIPv6 Internet Testing would be beneficial between major interop interop events events

• A mailing alias would be set up for further discussion on this t

A mailing alias would be set up for further discussion on this topic

• pic
• Presentation on this topic and other MIPv6 talks are found at

Presentation on this topic and other MIPv6 talks are found at http://www. http://www.connectathon connectathon.org .org

7 IETF56 March 17, 2003

Spec Issues Spec Issues

No Major Issues No Major Issues

Issues have been posted and discussed on the Issues have been posted and discussed on the mobileip mobileip alias alias

1. 1.

Section 11.5.4 should clarify that MN should respond to Section 11.5.4 should clarify that MN should respond to HA’s HA’s NS as a result of de NS as a result of de-

• registration BU from MN to HA

registration BU from MN to HA

2. 2.

MN movement detection may fail if the implementation uses MN movement detection may fail if the implementation uses

• nly NUD for default router address or only Prefix information
• nly NUD for default router address or only Prefix information

from RA from RA

3. 3.

Draft should clarify that HOTI/COTI/BU MUST not include RH Draft should clarify that HOTI/COTI/BU MUST not include RH and use home and use home-

• address as

address as dst dst when doing RO between two when doing RO between two MNs MNs

4. 4.

Should a CN send BE to MN when it receives BU with H bit ? Should a CN send BE to MN when it receives BU with H bit ?

5. 5.

Section 9.5.1 : Is the value 32784 correct ? Section 9.5.1 : Is the value 32784 correct ?

8 IETF56 March 17, 2003

Spec Issues Spec Issues

6. 6.

Should the spec specify that HA MUST not respond to a NS with Should the spec specify that HA MUST not respond to a NS with src src=HOA while it’s defending that HOA ? =HOA while it’s defending that HOA ?

7. 7.

CN should always send ICMPv6 or BE messages to source CN should always send ICMPv6 or BE messages to source address of the incoming packet without BCE lookup (clarification address of the incoming packet without BCE lookup (clarification

• nly)
• nly)

8. 8.

Can HA be CN for the same mobile node ? i.e. Should a HA/CN Can HA be CN for the same mobile node ? i.e. Should a HA/CN node ignore a BU (H bit on) while it’s serving as a CN for the node ignore a BU (H bit on) while it’s serving as a CN for the particular MN ? particular MN ?

Special Thanks to TAHI and UNH Test groups Special Thanks to TAHI and UNH Test groups