RE: Last Call: IPSec DOI Proposed Standard
Avram Shacham <shacham@cisco.com> Wed, 22 April 1998 18:55 UTC
Return-Path: shacham@cisco.com
Received: from bubbuh.cisco.com (bubbuh.cisco.com [198.92.30.35]) by ftp-eng.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id LAA29087 for <ippcp-archive-file@ftp-eng.cisco.com>; Wed, 22 Apr 1998 11:55:53 -0700 (PDT)
Received: from pita.cisco.com (pita.cisco.com [171.71.68.13]) by bubbuh.cisco.com (8.8.4-Cisco.1/CISCO.GATE.1.1) with ESMTP id LAA27741 for <ippcp@external.cisco.com>; Wed, 22 Apr 1998 11:55:06 -0700 (PDT)
Received: from shacham-home-pc-4.cisco.com ([171.71.69.80]) by pita.cisco.com (8.8.5-Cisco.1/8.6.5) with SMTP id LAA25400; Wed, 22 Apr 1998 11:54:30 -0700 (PDT)
Message-Id: <3.0.2.32.19980422115240.006d40d4@pita.cisco.com>
X-Sender: shacham@pita.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.2 (32)
Date: Wed, 22 Apr 1998 11:52:40 -0700
To: "'iesg@ns.ietf.org'" <iesg@ietf.org>
From: Avram Shacham <shacham@cisco.com>
Subject: RE: Last Call: IPSec DOI Proposed Standard
Cc: ipsec@tis.com, ippcp@external.cisco.com
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
The document <draft-ietf-ipsec-ipsec-doi-08> is inconsistent with the IP Payload Compression Protocol (IPComp) as defined in <draft-ietf-ippcp-protocol-05>. Regards, avram 4.4.5 IPSEC IPCOMP Transform Identifiers The IP Compression (IPCOMP) transforms define optional compression algorithms that can be negotiated to provide for IP compression before ESP encryption. ^^^^^^^^^^^^^^^^^^^^^ Is this very partial definition needed? 6.6 IPSEC IPCOMP Transform Identifiers The IPSEC IPCOMP Transform Identifier is an 8-bit value which ^^^^^I-D defines 1-63(6 bit) identifier a particular algorithm to be used to provide IP-level compression before ESP. Requests for assignments of new IPCOMP ^^^^^^^^^^^^^^^^^^^^^^ see above transform identifiers must be accompanied by a standards-track RFC which describes how to use the algorithm within the IPCOMP framework ([IPCOMP]). In addition, the requested algorithm must be published and in the public domain. If the requested algorithm is not in the public domain, the addition must be approved by an IESG action. The values 249-255 are reserved for private use amongst cooperating ^^^^^^^ 58-63? systems. === end of comments ===
- RE: Last Call: IPSec DOI Proposed Standard Avram Shacham
- Re: Last Call: IPSec DOI Proposed Standard Theodore Y. Ts'o
- Re: Last Call: IPSec DOI Proposed Standard Avram Shacham
- Re: Last Call: IPSec DOI Proposed Standard Naganand Doraswamy
- Re: Last Call: IPSec DOI Proposed Standard Derrell D. Piper
- Re: Last Call: IPSec DOI Proposed Standard Theodore Y. Ts'o
- Re: Last Call: IPSec DOI Proposed Standard Avram Shacham
- Re: Last Call: IPSec DOI Proposed Standard Theodore Y. Ts'o
- Re: Last Call: IPSec DOI Proposed Standard Avram Shacham
- Re: Last Call: IPSec DOI Proposed Standard Naganand Doraswamy