Re: [Idr] WG LC on draft-ietf-idr-large-community-03.txt (10/17/2016 to 10/31/2016)

Paul Jakma <paul@jakma.org> Fri, 21 October 2016 21:44 UTC

Return-Path: <paul@jakma.org>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DAE81295EF for <idr@ietfa.amsl.com>; Fri, 21 Oct 2016 14:44:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=jakma-org.20150623.gappssmtp.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 yKy-DhIWPnPU for <idr@ietfa.amsl.com>; Fri, 21 Oct 2016 14:44:06 -0700 (PDT)
Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B92961295ED for <idr@ietf.org>; Fri, 21 Oct 2016 14:44:05 -0700 (PDT)
Received: by mail-wm0-x236.google.com with SMTP id c78so7721967wme.0 for <idr@ietf.org>; Fri, 21 Oct 2016 14:44:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jakma-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:in-reply-to:message-id:references :user-agent:mime-version; bh=h8PIykjONl0mmxd1rSDWaGcI9jOL0oT4yF7CrtxOwuY=; b=WDftpkEc6iZC+tolOjb7zL74Ny+lP5x8it8XxxjTurxqEkIUVN1wjt1MMI3kOASnlP mKK1yX3MFXu6a4xnIC21m9Lb+f3UacozVTB3MV0a7fs/KHG23u+BtZhhP1gPLVA1zo52 7bt3EP98/Wr2160fQ0F5h49ZZMDJHZpZKhSSneWvbRLKik+XEhFBXdmk/8eHGwtluYV0 V5b7fQaXlCTrhkgUrsXcYX9nH08ZEy+wtfIAZ84YdOizGYdN9OY3vafGm7eenv1ozyH9 qM4+/dQM4ikR7I1GY2XMJ5BozX5ePltyI6XDT9HulcC8fANmNdkMUfwEx299JwI960RI CmsQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:in-reply-to:message-id :references:user-agent:mime-version; bh=h8PIykjONl0mmxd1rSDWaGcI9jOL0oT4yF7CrtxOwuY=; b=PkvVy3CKHzove3Z6w8YyoVNsr1yFvHfgsDLxne3pBxT8bljXIPVc4wN0p75VnNo32e U2QYjKU7ollMjWprupytaG0BSbKp02oi85DvTY/mPQTRVqSZCE7CnCb7cvEB6eZh6ZaZ ACjhMGncZ1WsMFXQXSF+awRAaiM5ZKdnh5ujl6PcYkzY9WI7oEsaVlLrBNthIUxh2OGe 9bKnE2+t2lN88N6PlW4ijQwJu3J6bNctV31A6/bCRmqhgr5S0uTOWCd56uKkUvgRgqD8 pXBaTwJBSUZ+45zr1m5wKVncu+pwrS5pvyGADoqf4TGWBOf5moJW1OBbzbkDe7q9+czP XeGA==
X-Gm-Message-State: AA6/9Rls2Z5AU9tTDDiYGV9EUs+VB2GGoqAf0li4otbAmbVzIK/UrbLfwyBGfylz+yG/2w==
X-Received: by 10.28.207.198 with SMTP id f189mr4695683wmg.18.1477086244300; Fri, 21 Oct 2016 14:44:04 -0700 (PDT)
Received: from espargaro.jakma.org ([2001:41c8:51:44:feff:ff:fe00:a2c]) by smtp.gmail.com with ESMTPSA id us3sm4889820wjb.32.2016.10.21.14.44.02 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 21 Oct 2016 14:44:02 -0700 (PDT)
Date: Fri, 21 Oct 2016 22:44:02 +0100 (BST)
From: Paul Jakma <paul@jakma.org>
To: "i3D.net - Martijn Schmidt" <martijnschmidt@i3d.net>
In-Reply-To: <2ddbfbaf-7b99-53b9-365c-269fcc7746e7@i3d.net>
Message-ID: <alpine.LRH.2.20.1610212236010.31112@espargaro.jakma.org>
References: <01f301d228b4$e3319ef0$a994dcd0$@ndzh.com> <20161017215134.GA464@pfrc.org> <20161018190851.GC15392@shrubbery.net> <20161018191521.GT95811@Vurt.local> <9EFC9BAA-F917-4C70-A139-1F69CAECF9C0@pfrc.org> <20161020215938.GE1074@Vurt.local> <adb00bcd7b8e45db857eae7019c646fc@XCH-ALN-014.cisco.com> <ae5da282-201c-f745-9f26-67ce73826bd5@i3d.net> <CA+b+ERkV2PBtzzx=uoygDzvTyJzunROCNX=0Y4phvGdn=oK5Xw@mail.gmail.com> <20161021154958.GR27221@gir.theapt.org> <CA+b+ERmrzCtFLP98D0YzRc-BJNbBWp3Ce6yKZr2cg1_QS0Oz5w@mail.gmail.com> <2ddbfbaf-7b99-53b9-365c-269fcc7746e7@i3d.net>
User-Agent: Alpine 2.20 (LRH 67 2015-01-07)
X-Snooper: A life spent reading others private email is a sad and wasted one
X-NSA: nitrate toxic DNDO hostage al aqsar fluffy jihad DHS cute musharef kittens jet-A1 ear avgas wax ammonium bad qran dog inshallah allah al-akbar martyr iraq hammas hisballah rabin ayatollah korea revolt mustard gas x-ray british airways hydrogen washington peroxide cool FEMA emergency four lions encryption ricin table pandemic scanner power sleet catalyst injection acetone toluene amatol
X-KEYSCORE: The greatest long-term threats to freedom and democracy are based in Langley and Fort Meade and Cheltenham
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/lGzOQ79u9UA5rQ37GQkLY7kl-7E>
Cc: IETF IDR WG <idr@ietf.org>, Peter Hessler <phessler@theapt.org>, Robert Raszuk <robert@raszuk.net>
Subject: Re: [Idr] WG LC on draft-ietf-idr-large-community-03.txt (10/17/2016 to 10/31/2016)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Oct 2016 21:44:07 -0000

On Fri, 21 Oct 2016, i3D.net - Martijn Schmidt wrote:

> Summarizing, any restrictions which can not be enforced don't belong 
> in the IDR document because they're irrelevant to implementors. 
> Arguing about it doesn't change the fact that such recommendations 
> belong in a BCP/GROW document. It is that simple.

Syntax can be in the protocol, without per se strictly enforcing the 
semantics - which could be defined elsewhere. A protocol document can 
say some 4-byte data is of type "IPv4 address" and another "ASN" without 
having to get into what that means - specifying how the type and data 
are encoded, while leaving the higher level semantics of the type(s) to 
other documents.

If we're going to encode a bunch of different typed things into a field, 
we might as well as provide a syntax for encoding type information into 
the field - at least for the obvious types of data we are _certain_ will 
be put in there. One of the types might well be "opaque data". ;)

m.v.g / regards,
-- 
Paul Jakma | paul@jakma.org | @pjakma | Key ID: 0xD86BF79464A2FF6A
Fortune:
No wonder you're tired!  You understood so much today.