IETF Logo Mail Archive

Re: [Int-area] Review of draft-ietf-intarea-provisioning-domains

Ted Lemon <mellon@fugue.com> Wed, 28 March 2018 15:51 UTC

Return-Path: <mellon@fugue.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C669127444 for <int-area@ietfa.amsl.com>; Wed, 28 Mar 2018 08:51:33 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.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 mXh5HtuoCUtL for <int-area@ietfa.amsl.com>; Wed, 28 Mar 2018 08:51:31 -0700 (PDT)
Received: from mail-qk0-x22a.google.com (mail-qk0-x22a.google.com [IPv6:2607:f8b0:400d:c09::22a]) (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 097BE120047 for <int-area@ietf.org>; Wed, 28 Mar 2018 08:51:31 -0700 (PDT)
Received: by mail-qk0-x22a.google.com with SMTP id d206so2898144qkb.0 for <int-area@ietf.org>; Wed, 28 Mar 2018 08:51:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=YCCoe3SIrr/WUjUznD+9Ro2kwLe5aBNN7Eqe4CIqrkk=; b=imGhgUEEmUFvaKckdEzcJ4I4To6CGMl+/xbYnmEpxktUanbnvxosO3PhX9waGZ8tNq ec7HsjoyMm2LKcDTy7rXnvPY9zTX4nz8YRWOxY3oqTsdtaXtxpHSLIqwC3Q4DZjjVQw6 OvljF69ZUk6pW+DOSESe1QVDxNzgdhI97u6fITWP2ya9/nGVocEW5AS5C/qUBpmNKsTC uHoV0tjGY2V1jkyUIYcUeebOH6S6oZX+6I008hGXqNHPxfttBFCTeuENwIBZTEMY3i3e SLjpPOBAJuzTMBzXMRqLyZtZbJgcC9IL7qSA2DeaEL23jnVpTbyfXViIRyzsct5JSqzT kzsg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=YCCoe3SIrr/WUjUznD+9Ro2kwLe5aBNN7Eqe4CIqrkk=; b=sFvmVwYtsioun3QV4sHuDS6EKuOBsDGUgVEVyLpYgGOczqEhdNeTr/JYGTsLK9w5lR oPS+lNiZyLg4+Uzfo2vklAmrJqgB7mg5c6fx9ZfmA+DJTidyf9Z9KKnmGFiD/DofdbYg aUrlyqwD9e6gTnixB2Gy1Pr0UEzc8guwugwii1OSm9k/vTa3g3Vrp1cjSYz9m1ZK8wg1 ZmhJljBPlf7CDB1ietbIFuvyQp5EQAPLdm+a/nq6bIwq5XT0+mA5LNdL3ciK1z1s6qsQ d0RgH8V6g47JfNy8Eun+asenUVECZ4JNFyA9bMswVjJORMcRTSYc+Twyt5UEt5z94IF0 MphA==
X-Gm-Message-State: ALQs6tAPDk/+sBs0J2dTMWC3wE4YXFKRpgB8DPoZV9sShFne4fbYX4CI wF9xMV4AiKmhGZ5BnooaSJ0UqNoeOEs=
X-Google-Smtp-Source: AIpwx48VTjZ8rZrdkpK+u33NtmL+ocFqjrrCeO0MXv7n0R4R4/ZgtPBaR88mBfO0ijcSmkXx+v3+Bw==
X-Received: by 10.55.11.18 with SMTP id 18mr5928880qkl.169.1522252290074; Wed, 28 Mar 2018 08:51:30 -0700 (PDT)
Received: from [10.0.1.12] ([8.20.190.66]) by smtp.gmail.com with ESMTPSA id q42sm2975535qtc.19.2018.03.28.08.51.29 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 28 Mar 2018 08:51:29 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <0F342CB4-0491-4A69-8A06-7A5F4EDC5D2A@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_F6FDD104-7EAD-413A-BDFA-AB19848F5CFA"
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
Date: Wed, 28 Mar 2018 11:51:26 -0400
In-Reply-To: <6E2B00DF-0AE9-4A14-9B82-2EA1B55308C6@cisco.com>
Cc: int-area <int-area@ietf.org>
To: "Eric Vyncke (evyncke)" <evyncke@cisco.com>
References: <EFB0BDF4-594A-44C5-BAA7-CBB8AEBADA41@fugue.com> <6E2B00DF-0AE9-4A14-9B82-2EA1B55308C6@cisco.com>
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/lGu27arYsEAhYCKjLp3hUPJpzTw>
Subject: Re: [Int-area] Review of draft-ietf-intarea-provisioning-domains
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Mar 2018 15:51:34 -0000

On Mar 28, 2018, at 10:53 AM, Eric Vyncke (evyncke) <evyncke@cisco.com> wrote:
> While the authors will review your comments and come back to the list, I want to stress that the HTTPS/JSON is really at the core of our proposal in order to add network information to the application (notably for CAPPORT WG or other).

Yup, I get that.   I don't personally have a big interest in the JSON bit, but I'm not saying don't do it—I'm just saying it doesn't mix well.  The two are sufficiently conceptually dissimilar that trying to mix them into the same document is really muddying the water, and I think it's actually preventing you from making the document as clear as it should be.   If you consider them as separate, related problems rather than a single problem I think you will find that both pieces of this solution benefit.

v2.23.0 | Report a Bug | By Email