Re: [stir] Getting PASSPORT Published

Mary Barnes <mary.ietf.barnes@gmail.com> Fri, 22 February 2019 03:45 UTC

Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: stir@ietfa.amsl.com
Delivered-To: stir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86AA312F295 for <stir@ietfa.amsl.com>; Thu, 21 Feb 2019 19:45:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 QlNya7xbIx01 for <stir@ietfa.amsl.com>; Thu, 21 Feb 2019 19:45:21 -0800 (PST)
Received: from mail-lj1-x232.google.com (mail-lj1-x232.google.com [IPv6:2a00:1450:4864:20::232]) (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 3F9C9126D00 for <stir@ietf.org>; Thu, 21 Feb 2019 19:45:21 -0800 (PST)
Received: by mail-lj1-x232.google.com with SMTP id q128so528681ljb.11 for <stir@ietf.org>; Thu, 21 Feb 2019 19:45:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=eJMrb8J2vO5EagxOVw5AtbRzcpLBWx+85UnLpJa8l9Q=; b=N6Yz2BCnON972sgiIpudQwJX7bG3CYnWvOwrs74DOVbB6mGdivQfwuLCY3kb5el/T8 y5UycrmiHLMAYLrVA0/AJTxRBEnvQAYQGzSsZwuC/gUDgmVg1JHra+vw1NYjhPZ8e0Po v5+OYKiwpvWSTlNiJTQI+xWPimdWjTYRz4jaRhZEUolByxBoPaks75S38g1xS5ptyJDr nZxTRz0nNoHdoBTeg82M+lV6yehLZSG9wT1rLq1YMJZOk/OcGykZXY8mTZjtqh24w59I KMO1O4AdkozUEMjiHrYUIGpZKHLm2q05Kcj6pSFwPp/WARdZqLoz+S+i3GJL20knSste 7fxQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=eJMrb8J2vO5EagxOVw5AtbRzcpLBWx+85UnLpJa8l9Q=; b=CDLExtgx+QA3cipbq/TTAQjjbHL883S2EslJZcXzPdt+0dQvAWsR+W74pAv//An78N QKeNl6TDrWOFlAkKNUrKx7kbEiEyKnk1LprXVQp2E3RK857NRlPECRa0YFEySdW+jEc+ /b6YOZVyRCasjFWw3PuM0OPGayaIteD3AB8+okNEDMMLRb4cH+iKdi9rNMG71zyUEBb9 lhqc0JW2Ucb+oWXhEgKOx2T032m8DPlPIt4anzlw25b5NCAMGsohJdT9V4fnkATvB7EW mJoG3sUTmRna68W39t12IhAomQe/Ky1vP6ZLQiD8rjiq86A6ZNlBmaMLa8PpIbL8xrHC ERUA==
X-Gm-Message-State: AHQUAubuRMFZ0GZrNWoI1Cj61G9z2xjzdZ+Ztb46klbP3qUmyuV1vwJP xHwOLH7PYAw23EQ+Jt4N+jg2drJ9XEzNHRbl2Ro=
X-Google-Smtp-Source: AHgI3IZQX7u1UYSPkGWV/Cc/jzJx6u4QOTVyBi8w7IP+/3Hr0j36Rs9u49vP9/js/PMBYsW5bJKyDizcSYXTDtQmneM=
X-Received: by 2002:a2e:425b:: with SMTP id p88mr961396lja.78.1550807119290; Thu, 21 Feb 2019 19:45:19 -0800 (PST)
MIME-Version: 1.0
References: <17d7e50b-5012-74ec-d1a5-9c8b80d60f4e@nostrum.com> <CAHBDyN70Mdtis2Z=XWGnExMz8g5Scuvy_XhcZ+VpnWkeXPddxQ@mail.gmail.com> <CAE3F73F-1B75-464E-BDAA-C1231A0EA81C@nostrum.com>
In-Reply-To: <CAE3F73F-1B75-464E-BDAA-C1231A0EA81C@nostrum.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
Date: Thu, 21 Feb 2019 21:45:08 -0600
Message-ID: <CAHBDyN4jbFdiMKHRKp+c6jUj_ORjSQXakK+2L+c2rvWqetrgSw@mail.gmail.com>
To: Ben Campbell <ben@nostrum.com>
Cc: Adam Roach <adam@nostrum.com>, draft-ietf-stir-passport-shaken.all@tools.ietf.org, "stir@ietf.org" <stir@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000075e7b50582736b41"
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/VLHnCoK3GmO5EWJNQoEnRbZaQU4>
Subject: Re: [stir] Getting PASSPORT Published
X-BeenThere: stir@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Secure Telephone Identity Revisited <stir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/stir>, <mailto:stir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/stir/>
List-Post: <mailto:stir@ietf.org>
List-Help: <mailto:stir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/stir>, <mailto:stir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Feb 2019 03:45:23 -0000

Hi Ben,

Thanks for your question.  I am more suggesting the former than the
latter.  Although, I also don't think the proposed change adds any real
value or will have any impact on what service providers choose to do.

Regards,
Mary

On Thu, Feb 21, 2019 at 5:52 PM Ben Campbell <ben@nostrum.com> wrote:

> <as individual>
>
> Hi Mary,
>
> Is your argument that the original text is good enough for an
> informational RFC, so there’s no need to improve it? Or that the proposed
> new text does not improve it?
>
> Thanks!
>
> Ben.
>
> > On Feb 21, 2019, at 5:12 PM, Mary Barnes <mary.ietf.barnes@gmail.com>
> wrote:
> >
> > I personally don't see it adds any value to make the proposed change
> given
> > that you're proposing to change the status of the draft to Informational
> > (which I'm fine with).  We've had this discussion many, many times with
> one
> > of those threads triggering this draft:
> > https://tools.ietf.org/html/draft-peterson-informational-normativity-01
> > We could start it again, if you don't agree with what that draft says -
> > that will give us a good topic for open mic discussions at the plenary
> next
> > month ;)
> >
> > I also thought IESG had published a statement on this, but I can only
> find
> > the one with regards to the references and not the terms:
> >
> https://www.ietf.org/blog/iesg-statement-normative-and-informative-references/
>
>