Brian,
> If we write a SHOULD we really do need some guidance
> as to when it doesn't apply. Otherwise we make it too
> easy for product managers to simply cross it off the list.
> How about
>
> The normal expectation is that a complete IPv6 stack
> includes an implementation of ESP. However,
Hello Ed,
We have been fighting this battle directly with government personal
at the Bureau of Industry and Security (http://www.bis.doc.gov/about/index.htm)
both by email and by phone. It has been going on for months. We finally
had a phone conversation with a higher level manager at BIS just t
If we write a SHOULD we really do need some guidance
as to when it doesn't apply. Otherwise we make it too
easy for product managers to simply cross it off the list.
How about
The normal expectation is that a complete IPv6 stack
includes an implementation of ESP. However, it is
recognized th
Sorry, that was a cut & paste mistake. AH is a MAY.
John
>-Original Message-
>From: ext Vishwas Manral [mailto:[EMAIL PROTECTED]
>Sent: 05 March, 2008 12:12
>To: Loughney John (Nokia-OCTO/PaloAlto)
>Cc: ipv6@ietf.org
>Subject: Re: Security Requirements for IPv6 Node Req summary
>
>Hi Jo
Hi John,
RFC4301 states AH is optional. Is there a reason why we are making it
a MUST be supported feature. Below quoting RFC4301:
"IPsec implementations MUST support ESP and MAY
support AH."
Thanks,
Vishwas
On Wed, Mar 5, 2008 at 11:46 AM, <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> The RFC
Hi all,
The RFC 4294-bis draft has the following requirement, which comes from
the initial RFC.
8.1. Basic Architecture
Security Architecture for the Internet Protocol [RFC-4301] MUST be
supported.
8.2. Security Protocols
ESP [RFC-4303] MUST be supported. AH [RFC-4302] MUST be supp
Hi,
The agenda for the 6man session for the Philadelphia IETF is posted at:
http://www.ietf.org/proceedings/08mar/agenda/6man.txt
Let us know if we missed anything.
The presenters should send us their slides the day before the meeting
so we can upload them to the IETF site so they will be
On Wednesday 13 February 2008, [EMAIL PROTECTED] wrote:
> Hi,
>
> I have posted a new version of the ikev2-ipv6-config draft
> (http://tools.ietf.org/id/draft-eronen-ipsec-ikev2-ipv6-config)
> which incorporates some new ideas based on good discussions
> in Vancouver (Hemant and Dave, thanks!).
>
>