Re: [Isis-wg] Kathleen Moriarty's No Objection on draft-ietf-isis-auto-conf-04: (with COMMENT)

Alia Atlas <akatlas@gmail.com> Thu, 13 April 2017 13:32 UTC

Return-Path: <akatlas@gmail.com>
X-Original-To: isis-wg@ietfa.amsl.com
Delivered-To: isis-wg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 110A812945F; Thu, 13 Apr 2017 06:32:57 -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, 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 tAWl5ALSNea5; Thu, 13 Apr 2017 06:32:54 -0700 (PDT)
Received: from mail-wr0-x229.google.com (mail-wr0-x229.google.com [IPv6:2a00:1450:400c:c0c::229]) (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 B1A45129471; Thu, 13 Apr 2017 06:32:52 -0700 (PDT)
Received: by mail-wr0-x229.google.com with SMTP id o21so35852002wrb.2; Thu, 13 Apr 2017 06:32: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=H6LiFpwkRUg52ik71iM/4XTNTF+/XDMm0rhPPPlibss=; b=UcQMc5k0pmsdabB69AGuH+d3GRLFTQOj7tI3CmO5LC6gXs0ON+5HW+/37nf7NmCcHe bseKGo+ezQwK5KdJ5HQHU8TWnSuQhhZD0wrNoXQ/gLZDjND4TWMcM6HY5mQo4EjPCgfG LNeIgOiFQqiFM5zOtyv4Jmqjc0kKnxMc4acYtQ6pQ25AOxAlGiWAGeTOUC4LKZgIF6rM NEUcj1Oxf0hkwLl/VFGwCM8DXR2ywYEVJKJli7p6xrtFdyuvAW5K81YO+fzCerhhaJ/2 n/i7rNAJvuYwAlsrWqOUPfUFWuVh4kaHVUNoGEDC8eBXCCgklQrLiALCCuNI6AWwko+Y 5unw==
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=H6LiFpwkRUg52ik71iM/4XTNTF+/XDMm0rhPPPlibss=; b=UbnbtA3kBYsrHygnRFg2t3PUgrU25TDsbx71ZpTuI4EsZFUKdAD4ZZSGOXqT/e8igL rOaB3AecJU2hpjXh10E/BjTEC9gEJiPkIOkYWjLnyJNHPM+XUydfDgeb+vIdbo+oDmVx vInhIDFgX0IQmFqRIHZXYjz2YDlSjrPpNp4g9x3Iz6FczaB7FIzpOh9r3o/+FhjkV+iZ KbCsH3qkoHcxAgWnsI7BSb6t3NFXRPln4fk0ccayAhgV41VxVfXp3mH7120ptEYTCiVU 8KWxsDI+K8gJH2l2p1TaLTMHMR9makmTd/TwKcwJBb0+im3dI7SevTivrRygK00iEYBy qcBQ==
X-Gm-Message-State: AN3rC/5faKX2VjyWkWZVBCCRh/9rrzSqs+Skd0642Afl4cM+Y74U85z1 PwlJgpdLnmUO7akTU256HvAI8GRbSw==
X-Received: by 10.223.133.152 with SMTP id 24mr3078588wrt.86.1492090371057; Thu, 13 Apr 2017 06:32:51 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.135.125 with HTTP; Thu, 13 Apr 2017 06:32:50 -0700 (PDT)
In-Reply-To: <CAHbuEH5VF5wr=Uhm8YJN2r6DSDkRZh3UvCcR_mE=t7VTe1m9Og@mail.gmail.com>
References: <149203479830.15702.1738541399483771065.idtracker@ietfa.amsl.com> <7f09ff867584402988655c661be59d3f@XCH-ALN-001.cisco.com> <CAHbuEH5VF5wr=Uhm8YJN2r6DSDkRZh3UvCcR_mE=t7VTe1m9Og@mail.gmail.com>
From: Alia Atlas <akatlas@gmail.com>
Date: Thu, 13 Apr 2017 09:32:50 -0400
Message-ID: <CAG4d1rcu4h9soKthA5HSUu3nt7f04Z4MRw+BMFAmRbjn0zJCiQ@mail.gmail.com>
To: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Cc: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, "draft-ietf-isis-auto-conf@ietf.org" <draft-ietf-isis-auto-conf@ietf.org>, "isis-wg@ietf.org" <isis-wg@ietf.org>, The IESG <iesg@ietf.org>, "isis-chairs@ietf.org" <isis-chairs@ietf.org>
Content-Type: multipart/alternative; boundary=001a11490fec8a4ac3054d0c5cdb
Archived-At: <https://mailarchive.ietf.org/arch/msg/isis-wg/DD7wh31IV_Q6suhN9ijFm2rvmX0>
Subject: Re: [Isis-wg] Kathleen Moriarty's No Objection on draft-ietf-isis-auto-conf-04: (with COMMENT)
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/isis-wg/>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Apr 2017 13:32:57 -0000

Hi Kathleen,

In this case, the generated identifiers are used for uniqueness so that each
router will have a different System ID.  The identifiers aren't used
otherwise.
The System IDs are flooded throughout the network as part of IS-IS.

I don't see a privacy concern here - but agree that it is good to step back
and
double-check.

Regards,
Alia

On Thu, Apr 13, 2017 at 8:39 AM, Kathleen Moriarty <
kathleen.moriarty.ietf@gmail.com> wrote:

> Hi Les,
>
> Thanks for your quick response.  My question is just at the comment
> level as I didn't see any issues, but just wanted to ask the question
> as I was not sure how the identifiers might be used.  If they are
> combined with user information or in use for home networking
> equipment, could user activity be traced.  Identifiers is one of the
> issues raised in RFC6973 and how they are used, even if they are
> randomly generated.
>
> Thanks,
> Kathleen
>
> On Wed, Apr 12, 2017 at 8:28 PM, Les Ginsberg (ginsberg)
> <ginsberg@cisco.com> wrote:
> > Kathleen -
> >
> > Thanx for the review. Inline.
> >
> >> -----Original Message-----
> >> From: Isis-wg [mailto:isis-wg-bounces@ietf.org] On Behalf Of Kathleen
> >> Moriarty
> >> Sent: Wednesday, April 12, 2017 3:07 PM
> >> To: The IESG
> >> Cc: draft-ietf-isis-auto-conf@ietf.org; isis-chairs@ietf.org;
> isis-wg@ietf.org
> >> Subject: [Isis-wg] Kathleen Moriarty's No Objection on
> draft-ietf-isis-auto-
> >> conf-04: (with COMMENT)
> >>
> >> Kathleen Moriarty has entered the following ballot position for
> >> draft-ietf-isis-auto-conf-04: No Objection
> >>
> >> When responding, please keep the subject line intact and reply to all
> email
> >> addresses included in the To and CC lines. (Feel free to cut this
> introductory
> >> paragraph, however.)
> >>
> >>
> >> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.
> html
> >> for more information about IESG DISCUSS and COMMENT positions.
> >>
> >>
> >> The document, along with other ballot positions, can be found here:
> >> https://datatracker.ietf.org/doc/draft-ietf-isis-auto-conf/
> >>
> >>
> >>
> >> ----------------------------------------------------------------------
> >> COMMENT:
> >> ----------------------------------------------------------------------
> >>
> >> Thanks for your response and updates to the SecDir review.
> >> https://mailarchive.ietf.org/arch/msg/secdir/_DxRs_eINTVE8E-
> >> N3S31Zr_10B8
> >>
> >> I don't see any privacy considerations with the identifiers created,
> discussed
> >> in System ID and Router-Fingerprint Generation Considerations and
> Section
> >> 3.2.  Are they in later documents that use these identifiers?
> >>  I see they may not be unique in home networks, but are there
> >> considerations for how they might be used that need to be documented?
> >> Thanks in advance.
> >
> > [Les:] The suggested values to be used to generate these identifiers are
> listed in Section 3.4.5:
> >
> >   o  MAC address(es)
> >
> >    o  Configured IP address(es)
> >
> >    o  Hardware IDs (e.g.  CPU ID)
> >
> >    o  Device serial number(s)
> >
> >    o  System clock at a certain specific time
> >
> >    o  Arbitrary received packet(s) on an interface(s)
> >
> > (though an implementation is free to use other identifiers).
> >
> > What about these suggestions indicates there is a privacy concern?
> >
> >    Les
> >
> >>
> >>
> >> _______________________________________________
> >> Isis-wg mailing list
> >> Isis-wg@ietf.org
> >> https://www.ietf.org/mailman/listinfo/isis-wg
>
>
>
> --
>
> Best regards,
> Kathleen
>
>