IETF Logo Mail Archive

[tcpm] Re: draft-ietf-tcpm-tcp-antispoof-01.txt

Joe Touch <touch@ISI.EDU> Sun, 06 November 2005 21:43 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EYsI5-0004d7-Eq; Sun, 06 Nov 2005 16:43:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EYsI3-0004cx-SI for tcpm@megatron.ietf.org; Sun, 06 Nov 2005 16:43:03 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21880 for <tcpm@ietf.org>; Sun, 6 Nov 2005 16:42:39 -0500 (EST)
Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EYsXW-0005jW-Kp for tcpm@ietf.org; Sun, 06 Nov 2005 16:59:04 -0500
Received: from [70.209.177.148] (148.sub-70-209-177.myvzw.com [70.209.177.148]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id jA6Lg8M04245; Sun, 6 Nov 2005 13:42:08 -0800 (PST)
Message-ID: <436E78A9.10609@isi.edu>
Date: Sun, 06 Nov 2005 13:42:01 -0800
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 1.4.1 (Windows/20051006)
MIME-Version: 1.0
To: Pekka Savola <pekkas@netcore.fi>
References: <4210B534.1010302@isi.edu> <426ED950.2010404@isi.edu> <Pine.LNX.4.61.0506171234000.25983@netcore.fi> <43485D5D.7040208@isi.edu> <Pine.LNX.4.64.0511062026140.2871@netcore.fi> <436E4F33.7070209@isi.edu> <Pine.LNX.4.64.0511062048590.3769@netcore.fi>
In-Reply-To: <Pine.LNX.4.64.0511062048590.3769@netcore.fi>
X-Enigmail-Version: 0.93.0.0
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Cc: tcpm@ietf.org
Subject: [tcpm] Re: draft-ietf-tcpm-tcp-antispoof-01.txt
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0563005716=="
Sender: tcpm-bounces@ietf.org
Errors-To: tcpm-bounces@ietf.org


Pekka Savola wrote:
> On Sun, 6 Nov 2005, Joe Touch wrote:
>>> There's extensive precedent for having Normative references [in]
>>> Informational documents and the IESG not barking on that.
>>
>> The IESG isn't the one that barks (they're asleep - consider the TCP
>> roadmap and discussion on the normative ref to an ID); it's the
>> RFC-Editor pass that catches these.
> 
> (Sorry, above I wrote "Normative references for", I meant to write
> "Normative references in".)
> 
> There is also extensive precedent for having norm references in
> informational documents and the RFC-editor appears to be fine with that.

Some. The larger issue is what it means to have a normative ref in a doc
that isn't itself a spec. Normative means 'referring to another spec in
a dependent way'. Sure, the other part is a spec - but how can a
non-spec 'depend' on a spec?

Joe


_______________________________________________
tcpm mailing list
tcpm@ietf.org
https://www1.ietf.org/mailman/listinfo/tcpm

v2.23.0 | Report a Bug | By Email