Re: [secdir] secdir review of draft-ietf-sipcore-content-id-06

Radia Perlman <radiaperlman@gmail.com> Tue, 27 June 2017 15:29 UTC

Return-Path: <radiaperlman@gmail.com>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35B16129B7E; Tue, 27 Jun 2017 08:29:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 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_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=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 JmLABCV_bojc; Tue, 27 Jun 2017 08:29:26 -0700 (PDT)
Received: from mail-oi0-x22e.google.com (mail-oi0-x22e.google.com [IPv6:2607:f8b0:4003:c06::22e]) (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 550BE129B5D; Tue, 27 Jun 2017 08:29:26 -0700 (PDT)
Received: by mail-oi0-x22e.google.com with SMTP id p66so19991038oia.0; Tue, 27 Jun 2017 08:29:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=rhdWy8vwDWL9Ah4JJrKlynDLK6w9ek24cqJV8eDdSXQ=; b=cXsAZuwjhf1/4YCxRXFancg61kmVlKwUKo4Ggx+Ur0lkomxJIc1ifsckZnrk1BBPcr +peiEIaubwEUkh//I2mRUQl59Ll7k7zz8W2oj9gTIaXGmC3PvNyGpygRmyR9vaebbA1t Of2HpXutRGZW6qmGE0i1C9mhO7yQTp2rPGGQvZ0Zc98S5G0YG6L8OwazzpNfX6yVJPOO VFfsWqIqCYjLdyMzudr3CAUxCf/HkRV+Rg7B0dgk+acK1UvBVH2vg8+YGeK23/QLV3YV modNRS7dmSISzl53Z1TW56e6YzJMPRyiox5YTalB+L06nQ7InE/+1dAEIRqbvnF2bJ2d vY/w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=rhdWy8vwDWL9Ah4JJrKlynDLK6w9ek24cqJV8eDdSXQ=; b=QL4F5/9f4Xy+TOn8F+lnZA6TzkK2F6ylTevtjGAjQP29d+IWqFQywBEDuVPdkuRKKb fSpReXJpZTPDjnNI15o6D43fufJsnuHOYQbIcqgQNH1QNzxgA61+YaFaeLkIV/61is0e hQDu0NkK+u5gfo+Alqdd9fvpKONAkaTlpPeeaUFPg+CKIYBuy81GrATYpqFIHvdgTpWE Y9WbHpj405pzIbxD4OJZDJnS1/5cFdJKBhtyvvyCEjvIAQ3df/z5MCUKnRAsQ1vnrGwp 0tbJIB6Q195/Po5tXbQwZbEX7n9xfVRfLS1qGhqMIozYqUfQ+K9qme2r1yrFXIHuEodR gtoQ==
X-Gm-Message-State: AKS2vOxfZl1ZP207xvCqc72+H0TZeVXHZQlwt+CVgnxcVWxXbu1w+r/M SoLOvZf8TI9SSc+xyK33n4EPMh0QcQ==
X-Received: by 10.202.192.5 with SMTP id q5mr3657037oif.60.1498577365723; Tue, 27 Jun 2017 08:29:25 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.145.37 with HTTP; Tue, 27 Jun 2017 08:29:25 -0700 (PDT)
In-Reply-To: <A407EE38-7918-444A-B9E8-C959DAAD35BB@nostrum.com>
References: <CAFOuuo7aRATmho-VrnTBC5soQjGBfD416TyOY2qjFA6fG0+9ig@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B4CC1C55A@ESESSMB109.ericsson.se> <BC29706C-AAC1-411D-8D0E-F20E9DBB5E27@nostrum.com> <7594FB04B1934943A5C02806D1A2204B4CC1E66C@ESESSMB109.ericsson.se> <A407EE38-7918-444A-B9E8-C959DAAD35BB@nostrum.com>
From: Radia Perlman <radiaperlman@gmail.com>
Date: Tue, 27 Jun 2017 08:29:25 -0700
Message-ID: <CAFOuuo4aZr4nnc=WO-KZPFSMTKQY51tvVVwzo0Tq9=7Z+YJvLQ@mail.gmail.com>
To: Ben Campbell <ben@nostrum.com>
Cc: Christer Holmberg <christer.holmberg@ericsson.com>, "draft-ietf-sipcore-content-id.all@ietf.org" <draft-ietf-sipcore-content-id.all@ietf.org>, The IESG <iesg@ietf.org>, "secdir@ietf.org" <secdir@ietf.org>
Content-Type: multipart/alternative; boundary="001a113dddfa8d76b20552f2bbe5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/ViCiDLDBJTrljT4JTmJBCdXRqSc>
Subject: Re: [secdir] secdir review of draft-ietf-sipcore-content-id-06
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdir/>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jun 2017 15:29:28 -0000

On Tue, Jun 27, 2017 at 8:07 AM, Ben Campbell <ben@nostrum.com> wrote:

>
> > On Jun 24, 2017, at 10:39 AM, Christer Holmberg <
> christer.holmberg@ericsson.com> wrote:
> >
>
> >> Would an informational reference to RFC 5411 (The Hitchhiker’s Guide to
> SIP) be helpful? Maybe if it
> >> were cited early in the introduction as a place to look for more
> information about the various SIP RFCs?
> >
> > I actually had a look in RFC 5411, but it doesn't clarify this.
> >
> > We have defined lots of new SIP header fields over the years, and I
> think people know how to "fit" them into the ABNF. Having said that, IF we
> want to clarify this, I think it should be done in 3261, 5411, or some
> other generic document.
> >
>
> I think that's a reasonable answer.
>
>
>
but I think it would be nice to have a couple of sentences in this RFC
saying "for an acronym list, see RFC xxx, for an overview of SIP concepts
see RFC xxx." rather than assuming that people will just read all the
normative references cited in the bibliography.