Re: [OPSAWG] Fwd: New Version Notification for draft-ietf-opsawg-mud-21.txt
"M. Ranganathan" <mranga@gmail.com> Thu, 17 May 2018 20:37 UTC
Return-Path: <mranga@gmail.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BE7912EB9C; Thu, 17 May 2018 13:37:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, 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 yXJbEe9n7GG3; Thu, 17 May 2018 13:36:53 -0700 (PDT)
Received: from mail-ot0-x22c.google.com (mail-ot0-x22c.google.com [IPv6:2607:f8b0:4003:c0f::22c]) (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 CF1891241FC; Thu, 17 May 2018 13:36:52 -0700 (PDT)
Received: by mail-ot0-x22c.google.com with SMTP id m11-v6so6591637otf.3; Thu, 17 May 2018 13:36:52 -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=Hgroz253J6WVN8PzDNRJd6qry79ImIRkRNKtJldKEXc=; b=R2z1Zm2LtGvgZdpF0g1+k2V4I/NRDMqIHC3ks3GUXtQAovgM6ECzrI/e7tXNimyi3b q+7jbhH5pUlZ66yjKWgd1quZ1PkukZBlWIGuStIR8t7IsppIJ/kKE15IyRhQhNSJbTVw GoTsGsyIQ7dHuEthY547RO7jISZS+Yr77tCnJ7ilQrnO52BjQSn27OJWb3b2DiNYogLV hVOHiBMlOWxlGbxRAUbBC5BG0JqAB9yi2ekYvftwcP6t3Xj00ObtEecY9zvFkCWpkXYD b+hxdmlcJFt6OLHPNk2kiifajcGlLUezmOyDLFNLCxL8/1Pa3zb/fLIYUyoG0LoWz2ki kdeQ==
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=Hgroz253J6WVN8PzDNRJd6qry79ImIRkRNKtJldKEXc=; b=CwX3l8hU1Zs78J8ceuxC1TFfd7VDvSF7snFr6sXLyP2ygPi1LziO9gHX8YdHP0imfS /ZFInZcb6TzSjNgXrzSs7jx7NPtCw9Tehj1SOAcc6knD+ntPBVqLBG7m++/QU8FbmTGd hYWt9TBnx7Ge+1ZZCo6EnXDzPIgBj8OAPtlLzHFHMrIU6xx5BM28zdJzkCGB9XmZucV8 LSf6Pw6D1nUgHf4HKqITjYHypb8+kwS8Bq4bLiaaCm9Ziog2lmVsat5gh4hxjIVHc32j dc8U942KmVrdy7JpOLIOjwj4ZURJOdarnxNMW8lYwPsYkdnOLZCk+rKsSVC/tFrv1bqu rP/A==
X-Gm-Message-State: ALKqPweH8j6+dxim2Jyl6Al0+cFEyTR8Tl7+5LkzkeXj6uhWC+T151MF j+HK2wn7Yl5qtq8aTzZb7EINlilAsJ9GU/tvVM4=
X-Google-Smtp-Source: AB8JxZojIM/zPYjKoTWVbJAfaapeKHiaTE6ELJiyRGu2t2QwH6i86D+96FfgV25qzyGplQ0OFYPJtoO0MhbaMj5s86o=
X-Received: by 2002:a9d:2bd6:: with SMTP id u80-v6mr4356347ota.51.1526589411859; Thu, 17 May 2018 13:36:51 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a9d:811:0:0:0:0:0 with HTTP; Thu, 17 May 2018 13:36:11 -0700 (PDT)
In-Reply-To: <8bafe1e0-12af-6526-d16e-6d39fded3bf3@cisco.com>
References: <152657039204.7694.840577957694607451.idtracker@ietfa.amsl.com> <8bafe1e0-12af-6526-d16e-6d39fded3bf3@cisco.com>
From: "M. Ranganathan" <mranga@gmail.com>
Date: Thu, 17 May 2018 16:36:11 -0400
Message-ID: <CAHiu4JOKvvZzU7vUUU9VaLJr784rLwOJBpZfxH79VymSCbfCkA@mail.gmail.com>
To: Eliot Lear <lear@cisco.com>
Cc: "opsawg@ietf.org" <opsawg@ietf.org>, IESG <iesg@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009ca41b056c6ccbf9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/-bz6-FOYsAFK_-Pat0MOYY5CXk0>
Subject: Re: [OPSAWG] Fwd: New Version Notification for draft-ietf-opsawg-mud-21.txt
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 May 2018 20:37:02 -0000
Hello Eliot, Thanks for the draft. Which version of access-control-list yang model does this depend on? I ask because if it is draft 19 of the ACL standard, I noticed a discrepancy in your example (possibly my mistake but I thought I should bring it to your attention): On page 52 should the following be changed to ietf-access-control-list:acls ? And also there's a similar one in the default Acls later in the draft. ietf-access-control-list:access-lists Thanks On Thu, May 17, 2018 at 11:36 AM, Eliot Lear <lear@cisco.com> wrote: > Hi everyone, > > This draft is intended to address all IESG comments. Thanks to the IESG > and reviewers for their contributions. A summary of the changes is below, > but people may wish to do a side by side review. > > Eliot > > > > - Small edits to the abstract > - Clarity in the introduction that the focus is on protecting the > device. > - Many grammatical/wording improvements > - Clarity when MUD is most effective. > - MUD controller -> MUD manager > - Normative language boiler plate change > - Clarity on what should happen when a MUD manager can't reach a MUD > file server > - A few reference updates > - Clarity on the validity time of a MUD file > - Added references to RFCs 5911 and 5912 for SMI changes > - one additional data element (documentation) > - one change based on an update to the ACL model during its last call > - Subsection numbering for node descriptions. > - Improved text around "controller", direction-initiated. > - Simplified MUD-URL text. > - Optional reserved space added to DHCP, LLDP options > - Simplified DHCP processing. > - A new certificate field to bind the manufacturer certificate to the > mud signer. > - A content type definition for the SMI. > - Updated security considerations. > > > > > ---------- Forwarded message ---------- > From: <internet-drafts@ietf.org> > To: Ralph Droms <rdroms@gmail.com>, Eliot Lear <lear@cisco.com>, Dan > Romascanu <dromasca@gmail.com> > Cc: > Bcc: > Date: Thu, 17 May 2018 08:19:52 -0700 > Subject: New Version Notification for draft-ietf-opsawg-mud-21.txt > > A new version of I-D, draft-ietf-opsawg-mud-21.txt > has been successfully submitted by Eliot Lear and posted to the > IETF repository. > > Name: draft-ietf-opsawg-mud > Revision: 21 > Title: Manufacturer Usage Description Specification > Document date: 2018-05-17 > Group: opsawg > Pages: 60 > URL: https://www.ietf.org/internet- > drafts/draft-ietf-opsawg-mud-21.txt > Status: https://datatracker.ietf.org/doc/draft-ietf-opsawg-mud/ > Htmlized: https://tools.ietf.org/html/draft-ietf-opsawg-mud-21 > Htmlized: https://datatracker.ietf.org/ > doc/html/draft-ietf-opsawg-mud > Diff: https://www.ietf.org/rfcdiff?url2=draft-ietf-opsawg-mud-21 > > Abstract: > This memo specifies a component-based architecture for manufacturer > usage descriptions (MUD). The goal of MUD is to provide a means for > end devices to signal to the network what sort of access and network > functionality they require to properly function. The initial focus > is on access control. Later work can delve into other aspects. > > This memo specifies two YANG modules, IPv4 and IPv6 DHCP options, an > LLDP TLV, a URL, an X.509 certificate extension and a means to sign > and verify the descriptions. > > > > > Please note that it may take a couple of minutes from the time of > submission > until the htmlized version and diff are available at tools.ietf.org. > > The IETF Secretariat > > > > _______________________________________________ > OPSAWG mailing list > OPSAWG@ietf.org > https://www.ietf.org/mailman/listinfo/opsawg > > -- M. Ranganathan
- [OPSAWG] Fwd: New Version Notification for draft-… Eliot Lear
- Re: [OPSAWG] Fwd: New Version Notification for dr… Joe Clarke
- Re: [OPSAWG] Fwd: New Version Notification for dr… Eliot Lear
- Re: [OPSAWG] Fwd: New Version Notification for dr… Joe Clarke
- Re: [OPSAWG] Fwd: New Version Notification for dr… M. Ranganathan
- Re: [OPSAWG] Fwd: New Version Notification for dr… Eliot Lear
- Re: [OPSAWG] Fwd: New Version Notification for dr… Joe Clarke
- Re: [OPSAWG] Fwd: New Version Notification for dr… Eric Rescorla
- Re: [OPSAWG] Fwd: New Version Notification for dr… Eliot Lear
- Re: [OPSAWG] Fwd: New Version Notification for dr… Eric Rescorla
- Re: [OPSAWG] Fwd: New Version Notification for dr… Eliot Lear
- Re: [OPSAWG] Fwd: New Version Notification for dr… Eric Rescorla
- Re: [OPSAWG] Fwd: New Version Notification for dr… Eliot Lear
- [OPSAWG] Fwd: New Version Notification for draft-… Eliot Lear