IETF Logo Mail Archive

Re: [tcpm] feedcback on tcp-secure-05

Randall Stewart <rrs@cisco.com> Thu, 13 July 2006 18:00 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G15UI-0000FW-Ek; Thu, 13 Jul 2006 14:00:34 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G15UG-0000FG-Hi for tcpm@ietf.org; Thu, 13 Jul 2006 14:00:32 -0400
Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G15UF-000262-82 for tcpm@ietf.org; Thu, 13 Jul 2006 14:00:32 -0400
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-2.cisco.com with ESMTP; 13 Jul 2006 11:00:31 -0700
X-IronPort-AV: i="4.06,238,1149490800"; d="scan'208"; a="328895525:sNHT25685824"
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-2.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id k6DI0UWj012020; Thu, 13 Jul 2006 11:00:30 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k6DI0OK6028274; Thu, 13 Jul 2006 11:00:30 -0700 (PDT)
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Thu, 13 Jul 2006 11:00:26 -0700
Received: from [127.0.0.1] ([171.68.225.134]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Thu, 13 Jul 2006 11:00:25 -0700
Message-ID: <44B68A3C.5000506@cisco.com>
Date: Thu, 13 Jul 2006 14:00:28 -0400
From: Randall Stewart <rrs@cisco.com>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060223
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Pekka Savola <pekkas@netcore.fi>
Subject: Re: [tcpm] feedcback on tcp-secure-05
References: <44B682AB.9010702@isi.edu> <Pine.LNX.4.64.0607132034230.8689@netcore.fi> <44B68831.5000307@isi.edu> <Pine.LNX.4.64.0607132055520.9253@netcore.fi>
In-Reply-To: <Pine.LNX.4.64.0607132055520.9253@netcore.fi>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 13 Jul 2006 18:00:26.0092 (UTC) FILETIME=[37FFA2C0:01C6A6A6]
DKIM-Signature: a=rsa-sha1; q=dns; l=1215; t=1152813630; x=1153677630; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=rrs@cisco.com; z=From:Randall=20Stewart=20<rrs@cisco.com> |Subject:Re=3A=20[tcpm]=20feedcback=20on=20tcp-secure-05; X=v=3Dcisco.com=3B=20h=3DEKS6OTHN/UpTjOxfSf0GHsnvOQo=3D; b=bLZMqRbYNMG1g97Bb9GGllvNnXHuEJU8SPTr45kazhxauzNGpsdXDNlmAduRP7pxCdiqJzvC 1SMMoxebhU4wIH4+iCHSQLuEs32+6+MzF6ewta+LH0YhJeoSJYg7dU4H;
Authentication-Results: sj-dkim-2.cisco.com; header.From=rrs@cisco.com; dkim=pass ( sig from cisco.com verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Cc: tcpm@ietf.org, Joe Touch <touch@ISI.EDU>
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>
Errors-To: tcpm-bounces@ietf.org

Pekka Savola wrote:
> On Thu, 13 Jul 2006, Joe Touch wrote:
> 
>>> On Thu, 13 Jul 2006, Joe Touch wrote:
>>>
>>>> The doc continues to have a detailed but somewhat incomplete discussion
>>>> of the attack scenario; the point of tcp-antispoof was to provide a 
>>>> much
>>>> more detailed version of that discussion that should not be
>>>> recapitulated but rather cited.
>>>
>>>
>>> You couldn't just simply cite it without any summary though, as
>>> antispoof is heading Informational, and doing so would likely require a
>>> down-ref.
>>
>>
>> It's not a down ref to cite an informational document informationally ;-)
> 
> 
> Sure.  But an Informative reference needs to refer to _additional_ 
> information, not _replace_ information.  So, with an informative 
> reference you will need to have at least short summary (a paragraph) of 
> the issues.
> 
Yep.. we could say something like..

For further reference information on these refer to ....

Note to Joe, the older revision of anti-spoof comes right
from the xml database... not sure why it did not snarf
your latest version..

R

-- 
Randall Stewart
NSSTG - Cisco Systems Inc.
803-345-0369 <or> 815-342-5222 (cell)

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

v2.23.0 | Report a Bug | By Email