Re: [bess] Referencing material behind a paywall

"Satya Mohanty (satyamoh)" <satyamoh@cisco.com> Wed, 19 December 2018 17:16 UTC

Return-Path: <satyamoh@cisco.com>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AE6F130E0E; Wed, 19 Dec 2018 09:16:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.502
X-Spam-Level:
X-Spam-Status: No, score=-14.502 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bR-MqBnezqZB; Wed, 19 Dec 2018 09:16:05 -0800 (PST)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 11A7D130E6E; Wed, 19 Dec 2018 09:16:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1040; q=dns/txt; s=iport; t=1545239765; x=1546449365; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=MekTAX+quaNwWdoY/rTEqBxLxaCiFU29r+IUsERpYiU=; b=YkCUP440Hj+pcVFnDDgda+w3fQ3QO8KZ6CMxtq7k/9TfK/g6KkijO3gu q02nVixex84xkeV04mvo5ZOE7ffsbWb/6xuqnWAeMjFz7QKET/PT66AMk dbWvbPx46H6h92EKAoAjc0mJ7FiV/Vzkux2qdPqkwmMfxANK+zmcp5m/F 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ADAABYexpc/51dJa1kGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAQGBUQQBAQEBAQsBggNmgQInCoNziBmLfIFoJZddgXsLAQE?= =?us-ascii?q?jhEkCF4JUIjQJDQEDAQECAQECbRwMhT0BBSMRRRACAQgYAgImAgICMBUQAQE?= =?us-ascii?q?EAQ0FgyIBggEPqCKBL4RBQIUqBYELizQXgUA/gTgME4JMgx4CAwGBdIJxMYI?= =?us-ascii?q?mAqE0CQKHDopSGJFZiUiEeYsaAhEUgScfOIFWcBVlAYJBixyFP0ExjUiBHwE?= =?us-ascii?q?B?=
X-IronPort-AV: E=Sophos;i="5.56,373,1539648000"; d="scan'208";a="215412988"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 19 Dec 2018 17:16:02 +0000
Received: from XCH-RTP-013.cisco.com (xch-rtp-013.cisco.com [64.101.220.153]) by rcdn-core-6.cisco.com (8.15.2/8.15.2) with ESMTPS id wBJHG18W021669 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 19 Dec 2018 17:16:02 GMT
Received: from xch-rtp-012.cisco.com (64.101.220.152) by XCH-RTP-013.cisco.com (64.101.220.153) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Wed, 19 Dec 2018 12:16:00 -0500
Received: from xch-rtp-012.cisco.com ([64.101.220.152]) by XCH-RTP-012.cisco.com ([64.101.220.152]) with mapi id 15.00.1395.000; Wed, 19 Dec 2018 12:16:00 -0500
From: "Satya Mohanty (satyamoh)" <satyamoh@cisco.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Heather Flanagan <rse@rfc-editor.org>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "Carsten Bormann" <cabo@tzi.org>
CC: "rtg-dir@ietf.org" <rtg-dir@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "bess@ietf.org" <bess@ietf.org>
Thread-Topic: Referencing material behind a paywall
Thread-Index: AdSOcFEaqToZ/E5HTCuKRToPwxsFLgCgl22AAAM89AABqW7MAA==
Date: Wed, 19 Dec 2018 17:16:00 +0000
Message-ID: <9D1896EC-081A-4192-A687-93ECC61B693C@cisco.com>
References: <0f2e01d48e72$b9581340$2c0839c0$@olddog.co.uk> <674294a6-29fc-691e-9feb-0a885c8756d4@rfc-editor.org> <cf355576-f1fa-813e-f3bd-7a0ff6579f14@cs.tcd.ie>
In-Reply-To: <cf355576-f1fa-813e-f3bd-7a0ff6579f14@cs.tcd.ie>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.121.97]
Content-Type: text/plain; charset="utf-8"
Content-ID: <43CE89E1B9F39C449EA204FC6FDDE2BC@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Outbound-SMTP-Client: 64.101.220.153, xch-rtp-013.cisco.com
X-Outbound-Node: rcdn-core-6.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/be5U-GlrV8oxVJNx1zdk1dOJvhs>
Subject: Re: [bess] Referencing material behind a paywall
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Dec 2018 17:16:07 -0000

Thank you Stephen, Carsten and Heather for your input.
Jorge will be publishing the revised version soon.

Best Regards,
--Satya

´╗┐On 12/10/18, 2:14 PM, "Stephen Farrell" <stephen.farrell@cs.tcd.ie> wrote:

    
    
    On 10/12/2018 20:41, Heather Flanagan wrote:
    > Ekr offered an interesting proposal that would have this kind of
    > reference be treated in a fashion similar to IPR declarations.
    
    Not a bad idea. I'd also make it like the downref registry [1]
    though, since once we've got a normative reference in one RFC
    to e.g. some IEEE 802 thing, then it shouldn't need new process
    to have a 2nd RFC do the same.
    
    Cheers,
    S.
    
    [1] https://datatracker.ietf.org/doc/downref/