spd for tunnel

Hi all, Please find the below example code for framing tunnel mode secured policy for a range of ipaddress. I am not able to create a security policy . Please help me to resolve this issue. INT32 ipsec_spd_add(INT32 dir, INT32 proto, INT32 level, INT8 * addr1, UINT16 sPort, INT8

Re: Last Call: draft-gennai-smime-cnipa-pec (Certified Electrinic Mail) to Proposed Standard

All, The I-D under LC, draft-gennai-smime-cnipa-pec, looks like a _first-class_ (counter-)example suitable to be fed into the IAB document Uncoordinated Protocol Development Considered Harmful (yet it's too late -- that's already shipped to the RFC Editor!). In this context, the provenance of the

SECDIR and OPSDIR review of draft-ietf-dhc-vpn-option-11

Hi, I have reviewed this document as part of the Security Directorate's ongoing effort to review all IETF documents being processed by the IESG. ... AND ... I have performed an unofficial Operations Directorate review. (i.e., I wasn't assigned as the OPSDIR reviewer) Background: This memo

spd tunnel mode

Hi all, Please find the below example code for framing tunnel mode secured policy for a range of ipaddress. I am not able to create a security policy . Please help me to resolve this issue INT32 ipsec_spd_add(INT32 dir, INT32 proto, INT32 level, INT8 * addr1, UINT16 sPort, INT8

Re: Gen-ART LC Review of draft-ietf-idnabis-rationale-13

thanks Ben, input much appreciated - minor comments can be addressed by the document editor. v On Oct 13, 2009, at 5:36 PM, Ben Campbell wrote: I have been selected as the General Area Review Team (Gen-ART) reviewer for this draft (for background on Gen-ART, please see

Re: I-D ACTION:draft-housley-iesg-rfc3932bis-10.txt

John, I do not personally have a problem with any of the suggested models, including yours. However, I have a problem in how we are discussing this topic. It has already been established a long time ago that you and many other people have strong opinions about this matter, and its easy to

Re: [Uri-review] [Fwd: [BEHAVE] Last Call: draft-ietf-behave-turn-uri (Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers) to Proposed Standard]

Howdy, I do not believe this document is ready for publication, as I believe the URI scheme documentation needs work. As it stands now, the scheme-specific processing required for this scheme is so great that I believe a standard URI parser will not work with the scheme as it is intended.

RE: [Uri-review] [Fwd: [BEHAVE] Last Call: draft-ietf-behave-turn-uri(Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers)to Proposed Standard]

-Original Message- From: ietf-boun...@ietf.org [mailto:ietf-boun...@ietf.org] On Behalf Of Ted Hardie Sent: Thursday, October 15, 2009 2:34 PM To: Magnus Westerlund Cc: uri-rev...@ietf.org; ietf@ietf.org; app-...@tools.ietf.org Subject: Re: [Uri-review] [Fwd: [BEHAVE] Last Call:

Re: [Uri-review] [Fwd: [BEHAVE] Last Call: draft-ietf-behave-turn-uri (Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers) to Proposed Standard]

Hi Marc, Thanks for your reply. Some further comments below. On Thu, Oct 15, 2009 at 4:20 PM, Marc Petit-Huguenin m...@petit-huguenin.org wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Ted, Thanks for reviewing this I-D.  See my comments below. Ted Hardie wrote: Howdy, I do

Re: [Uri-review] [Fwd: [BEHAVE] Last Call: draft-ietf-behave-turn-uri(Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers)to Proposed Standard]

On Thu, Oct 15, 2009 at 6:03 PM, Dan Wing dw...@cisco.com wrote: I requested review by uri-review on 30-JUL-2009, per your earlier suggestion.  However, we received no review comments from that request, which was mentioned in the PROTO write-up for this document.  This is my only experience

Re: I-D ACTION:draft-housley-iesg-rfc3932bis-10.txt

Jari, Jari Arkko wrote: It is not news that what we proposed as a compromise position isn't optimal from some people's point of view. But a small number of voices should not drive the entire community's choice. We agree, yet oddly land on different sides. A review of the public record

Weekly posting summary for ietf@ietf.org

Total of 93 messages in the last 7 days. script run at: Fri Oct 16 00:53:02 EDT 2009 Messages | Bytes| Who +--++--+ 8.60% |8 | 8.65% |64004 | o...@cisco.com 2.15% |2 | 11.39% |84272 | rich...@shockey.us

Last Call: draft-ietf-behave-turn-uri (Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers) to Proposed Standard

The IESG has received a request from the Behavior Engineering for Hindrance Avoidance WG (behave) to consider the following document: - 'Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers ' draft-ietf-behave-turn-uri-03.txt as a Proposed Standard The IESG plans to make a

Document Action: 'Security Threats and Security Requirements for the Access Node Control Protocol (ANCP)' to Informational RFC

The IESG has approved the following document: - 'Security Threats and Security Requirements for the Access Node Control Protocol (ANCP) ' draft-ietf-ancp-security-threats-08.txt as an Informational RFC This document is the product of the Access Node Control Protocol Working Group. The

Document Action: 'Transport Layer Security (TLS) Authorization Extensions' to Experimental RFC

The IESG has approved the following document: - 'Transport Layer Security (TLS) Authorization Extensions ' draft-housley-tls-authz-extns-09.txt as an Experimental RFC This document has been reviewed in the IETF but is not the product of an IETF Working Group. The IESG contact person is Tim

Protocol Action: 'iCalendar Transport-Independent Interoperability Protocol (iTIP)' to Proposed Standard

The IESG has approved the following document: - 'iCalendar Transport-Independent Interoperability Protocol (iTIP) ' draft-ietf-calsify-2446bis-10.txt as a Proposed Standard This document is the product of the Calendaring and Scheduling Standards Simplification Working Group. The IESG

WG Action: Multipath TCP (mptcp)

A new IETF working group has been formed in the Transport Area. For additional information, please contact the Area Directors or the WG Chairs. Multipath TCP (mptcp) --- Current Status: Active Working Group Chairs: Philip Eardley

Last Call: draft-ietf-geopriv-lis-discovery (Discovering the Local Location Information Server (LIS)) to Proposed Standard

The IESG has received a request from the Geographic Location/Privacy WG (geopriv) to consider the following document: - 'Discovering the Local Location Information Server (LIS) ' draft-ietf-geopriv-lis-discovery-11.txt as a Proposed Standard The IESG plans to make a decision in the next few