[IPsec] RFC5996bis editorial change in section 3.2 Generic Payload Header (Was One more editorial issue in RFC5996)

Tero Kivinen <kivinen@iki.fi> Tue, 12 November 2013 19:53 UTC

Return-Path: <kivinen@iki.fi>
X-Original-To: ipsec@ietfa.amsl.com
Delivered-To: ipsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9016911E811B for <ipsec@ietfa.amsl.com>; Tue, 12 Nov 2013 11:53:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.586
X-Spam-Level:
X-Spam-Status: No, score=-102.586 tagged_above=-999 required=5 tests=[AWL=0.013, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G9fu5iMYjQm0 for <ipsec@ietfa.amsl.com>; Tue, 12 Nov 2013 11:53:49 -0800 (PST)
Received: from mail.kivinen.iki.fi (fireball.kivinen.iki.fi [IPv6:2001:1bc8:100d::2]) by ietfa.amsl.com (Postfix) with ESMTP id BF52E21F9EED for <ipsec@ietf.org>; Tue, 12 Nov 2013 11:53:36 -0800 (PST)
Received: from fireball.kivinen.iki.fi (localhost [127.0.0.1]) by mail.kivinen.iki.fi (8.14.7/8.14.5) with ESMTP id rACJrY5Z024021 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 12 Nov 2013 21:53:34 +0200 (EET)
Received: (from kivinen@localhost) by fireball.kivinen.iki.fi (8.14.7/8.12.11) id rACJrYug008640; Tue, 12 Nov 2013 21:53:34 +0200 (EET)
X-Authentication-Warning: fireball.kivinen.iki.fi: kivinen set sender to kivinen@iki.fi using -f
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID: <21122.34622.118634.864403@fireball.kivinen.iki.fi>
Date: Tue, 12 Nov 2013 21:53:34 +0200
From: Tero Kivinen <kivinen@iki.fi>
To: Valery Smyslov <svanru@gmail.com>
In-Reply-To: <2FA74E8177C2445E82D929E4857FA377@buildpc>
References: <21087.60447.758422.672867@fireball.kivinen.iki.fi> <7C1EFED8998C4309B562F2224DD39AA2@buildpc> <2FA74E8177C2445E82D929E4857FA377@buildpc>
X-Mailer: VM 8.2.0b under 24.3.1 (x86_64--netbsd)
X-Edit-Time: 1 min
X-Total-Time: 0 min
Cc: ipsec@ietf.org
Subject: [IPsec] RFC5996bis editorial change in section 3.2 Generic Payload Header (Was One more editorial issue in RFC5996)
X-BeenThere: ipsec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion of IPsec protocols <ipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipsec>, <mailto:ipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipsec>
List-Post: <mailto:ipsec@ietf.org>
List-Help: <mailto:ipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipsec>, <mailto:ipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Nov 2013 19:53:49 -0000

Valery Smyslov writes:
> Just came across one more small editorial issue in RFC5996.
> Page 73, description of "Next Payload" field, sentence
> 
>       In the header of an Encrypted payload, the Next Payload field is set
>       to the payload type of the first contained payload (instead of 0);
>       conversely, the Next Payload field of the last contained payload
>       is set to zero).  
> 
> has extra round bracket at the end.

Removed.
-- 
kivinen@iki.fi