[dispatch] draft-atarius-dispatch-meid-urn-as-instanceid and RFC 7255

worley@ariadne.com (Dale R. Worley) Thu, 14 December 2017 03:37 UTC

Return-Path: <worley@alum.mit.edu>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7230D1276AF for <dispatch@ietfa.amsl.com>; Wed, 13 Dec 2017 19:37:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.934
X-Spam-Level:
X-Spam-Status: No, score=-1.934 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
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 RAGfHcpwG_Xg for <dispatch@ietfa.amsl.com>; Wed, 13 Dec 2017 19:37:33 -0800 (PST)
Received: from resqmta-ch2-06v.sys.comcast.net (resqmta-ch2-06v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3C44A126DD9 for <dispatch@ietf.org>; Wed, 13 Dec 2017 19:37:33 -0800 (PST)
Received: from resomta-ch2-04v.sys.comcast.net ([69.252.207.100]) by resqmta-ch2-06v.sys.comcast.net with ESMTP id PKKye28Ed5x03PKKyeFrqF; Thu, 14 Dec 2017 03:37:32 +0000
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-ch2-04v.sys.comcast.net with SMTP id PKKxe2ojNnshJPKKxecb8P; Thu, 14 Dec 2017 03:37:32 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id vBE3bU0f021460; Wed, 13 Dec 2017 22:37:30 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id vBE3bUdw021457; Wed, 13 Dec 2017 22:37:30 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com
To: dispatch@ietf.org, draft-atarius-dispatch-meid-urn-as-instanceid.all@ietf.org
In-Reply-To: <201712111543.vBBFhFPn040652@givry.fdupont.fr> (Francis.Dupont@fdupont.fr)
Sender: worley@ariadne.com
Date: Wed, 13 Dec 2017 22:37:29 -0500
Message-ID: <87zi6mx9mu.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4wfD+xwXyVjih1EmEfhJdErfEQYQLHo4EyI2MxBwVxbokmug93MWdFDUv1VZnXkTFKKDWuKp0ytwqibYLncsu5Y0vA/PsAqAqyzZDek56GZyA/y3ll+qD2 HFrJAPA4F0xTHsnO9671SxHRBQRYoqdCavEvEkHMcwVhXO7nh7OUJbUYU87QouX8W15061RS+LLiKzjpT87RJaxQY0plL3c6tyMaYJfnTSggCZa16nV6fA6b JBYCP7RDtrnA63hSGCAKqw==
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/xHt1mAfcCDzqHbQiSLz5kfIHero>
Subject: [dispatch] draft-atarius-dispatch-meid-urn-as-instanceid and RFC 7255
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Dec 2017 03:37:34 -0000

IMHO, this draft should describe its relationship with RFC 7255 in more
detail:  What is the difference between MEID and IMEI?  Why is an MEID
URN better than an IMEI URN, or at least, why can MEID be used in
situations when IMEI cannot?

That is, what does this draft enable that RFC 7255 has not already
enabled?

(I'm sure these questions have a good answer, or the authors wouldn't
have writte this draft, but the answers aren't in this draft.)

Dale