[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: WGLC: draft-ietf-v6ops-cpe-simple-security-10.txt

To: "Laganier, Julien" <julienl@qualcomm.com>
Subject: Re: WGLC: draft-ietf-v6ops-cpe-simple-security-10.txt
From: james woodyatt <jhw@apple.com>
Date: Tue, 20 Apr 2010 10:43:28 -0700
Cc: IPv6 Operations <v6ops@ops.ietf.org>
In-reply-to: <BF345F63074F8040B58C00A186FCA57F1EFEFD6EBB@NALASEXMB04.na.qualcomm.com>
References: <118FE8EC-41DF-4907-AE1C-2B7185477D64@cisco.com> <BF345F63074F8040B58C00A186FCA57F1EFEFD6EBB@NALASEXMB04.na.qualcomm.com>

On Apr 20, 2010, at 09:17, Laganier, Julien wrote:
> 
> I believe we should cover MIPv6 adequately in this specification by adding explicit tracking of outbound initiated MIPv6 HoA/RH2 degenerated tunnels. 
> 
> [ The MEXT WG has two documents specifying firewall behavior for MIPv6 that could be used as a starting point for text to be included in this spec -- see http://tools.ietf.org/html/draft-ietf-mext-firewall-vendor-02 and http://tools.ietf.org/html/draft-ietf-mext-firewall-admin-02 ]

This is an important technical point.  I will review those drafts and send a revision to I-D.ietf-v6ops-cpe-simple-security shortly.


--
james woodyatt <jhw@apple.com>
member of technical staff, communications engineering

References:
- WGLC: draft-ietf-v6ops-cpe-simple-security-10.txt
  - From: Fred Baker <fred@cisco.com>
- RE: WGLC: draft-ietf-v6ops-cpe-simple-security-10.txt
  - From: "Laganier, Julien" <julienl@qualcomm.com>

Prev by Date: Re: FYI: DNSOPS presentation
Next by Date: Re: I-D.ietf-v6ops-cpe-simple-security-10
Previous by thread: Re: WGLC: draft-ietf-v6ops-cpe-simple-security-10.txt
Next by thread: RE: WGLC: draft-ietf-v6ops-cpe-simple-security-10.txt
Index(es):
- Date
- Thread