Re: SDNAuth - Secure SDN authentication and authorization - Interested?

Dave Cridland <dave@cridland.net> Wed, 04 February 2015 21:18 UTC

Return-Path: <dave@cridland.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B3011A88B7 for <ietf@ietfa.amsl.com>; Wed, 4 Feb 2015 13:18:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level:
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 rGq429oGWI6A for <ietf@ietfa.amsl.com>; Wed, 4 Feb 2015 13:18:55 -0800 (PST)
Received: from mail-oi0-x22b.google.com (mail-oi0-x22b.google.com [IPv6:2607:f8b0:4003:c06::22b]) (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 426E71A8821 for <ietf@ietf.org>; Wed, 4 Feb 2015 13:18:55 -0800 (PST)
Received: by mail-oi0-f43.google.com with SMTP id z81so3420387oif.2 for <ietf@ietf.org>; Wed, 04 Feb 2015 13:18:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=PifWoYkrASRYgFIzxZNJJCswEtLFnFX41y3CMbDQnsM=; b=AhHenKbrU3tX82ttT2f/52Tc5HoeDaKwgWSqWlc9SsezkTGAyKQSFwIG8QJCzghZRs QDmkNBDLSw+/g0NwTTXKM0Guibe3wOE9LvhaTo3Sta5iiGtKnu2z5bKSY00oU94iwMcl QDVe25pFJd2UdnnB63O6Nx4Qq+TQhr+qpVuso=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=PifWoYkrASRYgFIzxZNJJCswEtLFnFX41y3CMbDQnsM=; b=C26m5Rq2Ch7P+1cv2Zl35OOwSStfIE1nKhuPghIS95cm/aVr3ZvYwhhh0DPTiCvrbM K/l3NoCZdcrgIjA3Xd57NSFKUas3Vr4//BbMuWEraedHdpioNy0PJxU/8pyT0FW7cU1Q DWABRKd+ObfYYpzxWFiHj3La5bwoWiy1lm5OTfezgzvrola1ZS7gRXNMImq3NkTbHn4z j6W64Xy5jeQr+sFEXyuvfvEm9zdei0ASnapQff4V8Ej0u8+hnxuvJz7YzmUm6B7JTzMs Bw88Dx1uBQPxQNBHHRi187HVNPgOOFSTKARSZiQ/rENZz7YKkfLfKDNIqfWfF70B2cxg 2Kkg==
X-Gm-Message-State: ALoCoQnvn9Q/fdSd16hFnQkZm4Pj6Ril/P42QYMN3Vio5aX7w0L7FGsbO4Z0QyxEtfgBxt2t6mMg
MIME-Version: 1.0
X-Received: by 10.182.44.132 with SMTP id e4mr233629obm.86.1423084734489; Wed, 04 Feb 2015 13:18:54 -0800 (PST)
Received: by 10.60.77.71 with HTTP; Wed, 4 Feb 2015 13:18:54 -0800 (PST)
Received: by 10.60.77.71 with HTTP; Wed, 4 Feb 2015 13:18:54 -0800 (PST)
In-Reply-To: <CAHbuEH5mdyQggfJxRwnYnv2meaO8NwQJ-g4=ZXVLF85CjjeXtg@mail.gmail.com>
References: <012901d03692$cdc46630$694d3290$@rozanak.com> <CA+9kkMApUS=y0zNg7GDHGogU9tG=s=WwuEuy=OGdQAdCuYczOg@mail.gmail.com> <54D17283.7080708@gondrom.org> <EB9AAE7B-9756-4CB2-8CB2-CEB973306C82@nominum.com> <54D22CC4.6040305@gondrom.org> <CAKHUCzxEhaLysZKkcQnFfPB-9OZqhzbup6==8E8e6LAKJ33oFQ@mail.gmail.com> <CAHbuEH7DAFtzCbTY0TZM2WJmU3QAG0EUqEYw=q223E3cceOd_w@mail.gmail.com> <CAKHUCzzCUqYDt9sztDVAJpk-abqXXgmuaSAv0yvcOC2_c9c3TQ@mail.gmail.com> <CAHbuEH5mdyQggfJxRwnYnv2meaO8NwQJ-g4=ZXVLF85CjjeXtg@mail.gmail.com>
Date: Wed, 04 Feb 2015 21:18:54 +0000
Message-ID: <CAKHUCzwHu+ziij227j-mqNwBJpfZGkh-G230QZR5GpNrqbcgFQ@mail.gmail.com>
Subject: Re: SDNAuth - Secure SDN authentication and authorization - Interested?
From: Dave Cridland <dave@cridland.net>
To: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="001a11c2f49a15be16050e49bcd8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/rkr05b6w48qgxTbkcymmSjdXbxM>
Cc: Ted Hardie <ted.ietf@gmail.com>, "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Feb 2015 21:18:57 -0000

That's much clearer, and to my mind more worrying.

Any discussion outside of the IETF is outside the IETF, whether it's within
a group, or a list, or a pub on the corner, or whatever. The IETF surely
cannot impose its IPR rules to the world at large.

If the results of that discussion are later entered as a contribution to
the IETF, the IETF's IPR rules apply to the person contributing, not to the
originator.

If the list discussion needs to happen under the IETF rules, the list needs
to be formally an IETF one.

Note that I'm not concerned with the specifics of whether this list ought
to exist or whether the goals are defined - just whether an non-IETF list
should be under IETF rules.
On 4 Feb 2015 21:02, "Kathleen Moriarty" <kathleen.moriarty.ietf@gmail.com>
wrote:

> On Wed, Feb 4, 2015 at 3:49 PM, Dave Cridland <dave@cridland.net> wrote:
> > So you want this list to be under IETF rules, because it's intended that
> > IETF contributions will happen from it, but you don't want it to be an
> IETF
> > list, because people might treat it as being IETF contributions.
>
> My request was in the list of steps I provided to Hosnieh and that was
> just to ensure that those contributing to a draft outside of IETF
> understand that the NoteWell applies to content on that draft to be
> contributed.  It's important for this to be understood by
> contributors.  My request was for her to work with a small group and I
> never suggested a list.  I sent her this list several weeks ago along
> with a private note to help her with next steps.  The list I sent her
> is the same that I posted.
>
> I'm going to get back to reading drafts and not answer for others in
> this discussion.
>
> Best regards,
> Kathleen
>
> >
> > I see there's a distinction, I'm not clear why it was drawn, but I'll
> take
> > your word for it that it's not as political as it sounds.
> >
> > On 4 Feb 2015 20:27, "Kathleen Moriarty" <
> kathleen.moriarty.ietf@gmail.com>
> > wrote:
> >>
> >> Hi Dave,
> >>
> >> I didn't read this thread the same way you did.  I read it as Ted
> >> pointing out that the Notewell will be important for contributors to
> >> understand applies for any submission that comes to the IETF.
> >>
> >> You can look at the SecAuth archive to see why it was shutdown.  Many
> >> were glad as the work was taking too long to become focused into an
> >> achievable set of goals.  A push to go back to the drawing board was
> >> needed.  If it's an IETF list, many feel they have to follow it and
> >> the work wasn't ready for that yet.  We'll re-evaluate the proposal
> >> when they have had time to narrow the scope and figure out what
> >> problem they want to solve most.
> >>
> >> Best regards,
> >> Kathleen
> >>
> >> On Wed, Feb 4, 2015 at 3:08 PM, Dave Cridland <dave@cridland.net>
> wrote:
> >> > Do I understand this right? The original mailing list was shut down by
> >> > the
> >> > IETF, and folks are now complaining that the third party list isn't an
> >> > IETF
> >> > one? Seriously?
> >> >
> >> > On 4 Feb 2015 14:29, "Tobias Gondrom" <tobias.gondrom@gondrom.org>
> >> > wrote:
> >> >>
> >> >> On 04/02/15 21:12, Ted Lemon wrote:
> >> >>
> >> >> On Feb 3, 2015, at 6:14 PM, Tobias Gondrom <
> tobias.gondrom@gondrom.org>
> >> >> wrote:
> >> >>
> >> >> just fyi: the mailing-list does on its sign-up page (in the first
> line)
> >> >> make the explicit statement to operate under the IETF
> >> >> Notewell:https://mail.rozanak.com/mailman/listinfo/sdnauth
> >> >>
> >> >> That's precisely what I would advise doing in this situation.   It
> >> >> might
> >> >> be worth adding that the list is informal and is not sponsored by the
> >> >> IETF,
> >> >> though; otherwise people might get the impression that it's an
> official
> >> >> IETF
> >> >> mailing list.   You should also disclose whether or not the list is
> >> >> being
> >> >> archived, although since it's not an IETF mailing list, whether you
> do
> >> >> so is
> >> >> not up to us.   If the list is not archived, however, it might be
> >> >> difficult
> >> >> and involve a painful discovery process if for some reason the Note
> >> >> Well had
> >> >> to be enforced in a lawsuit.  So while keeping an archive places an
> >> >> additional burden on Hosnieh, it is probably a win for other
> >> >> participants.
> >> >>
> >> >> (And yes, I realize you were talking to the other Ted... :)
> >> >>
> >> >>
> >> >> Just fyi: I am not the administrator of the mailing-list. I just
> >> >> happened
> >> >> to sign-up and noticed that the notewell is/was already there on the
> >> >> sign-up
> >> >> page. It seems the new list only got needed up as the Sec AD
> (Kathleen)
> >> >> shut
> >> >> down the previous IETF BOF mailing-list.
> >> >>
> >> >> And to answer your second question: it appears the new list is being
> >> >> archived, as is also a basic mailman function.
> >> >>
> >> >> Best regards, Tobias
> >>
> >>
> >>
> >> --
> >>
> >> Best regards,
> >> Kathleen
>
>
>
> --
>
> Best regards,
> Kathleen
>