Re: [Add] Authentication Sub-topics for Tuesday Interim (homework for Tuesday's meeting)

tirumal reddy <kondtir@gmail.com> Mon, 14 September 2020 07:50 UTC

Return-Path: <kondtir@gmail.com>
X-Original-To: add@ietfa.amsl.com
Delivered-To: add@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5ECFC3A0D24 for <add@ietfa.amsl.com>; Mon, 14 Sep 2020 00:50:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.197
X-Spam-Level:
X-Spam-Status: No, score=-0.197 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=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 xKUsoKKzNhU7 for <add@ietfa.amsl.com>; Mon, 14 Sep 2020 00:50:38 -0700 (PDT)
Received: from mail-il1-x12c.google.com (mail-il1-x12c.google.com [IPv6:2607:f8b0:4864:20::12c]) (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 315323A0D20 for <add@ietf.org>; Mon, 14 Sep 2020 00:50:38 -0700 (PDT)
Received: by mail-il1-x12c.google.com with SMTP id t12so4678371ilh.3 for <add@ietf.org>; Mon, 14 Sep 2020 00:50:38 -0700 (PDT)
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=sKOxOY3XanO13TnOqez0HlZOsi5k59meVoScui6siog=; b=N0AOATSzXw1gEFKUgB1bBZR0e1kUI+wI6d4L4Yig8+F66r0UuNaf4gUfNMGX69DixC Wi0df9KJgMkmicIJQuLoGUKNdfPvfY7PC9Xd/4BXQPcF0xAoRUu5qp9ZPJye3k5uHt/6 kPLfdgubtPtH+9pfnF8Uw2ZPs7sHjjBgkh84j57+Hxo8QjlhZlSr5eCuTQJJOcc1djzk o0ykbaxQ/ogF+4zQ5CfOLZQyHDTA8D3KWIZTqR1AxBfPYc9uLRrXM+wQXVJy3bqTQDYs sGJCmIO2Zic7Axy7RmM2wW1TNYH8TlWRVqA6FOeN9MIN+DeMGfjMR6jtTbP+HDzU6YPd FZlw==
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=sKOxOY3XanO13TnOqez0HlZOsi5k59meVoScui6siog=; b=gWIzdU98Ip5j6ZWmXF2V5n6FpQyOPX6rYKH1J9eQIdOwFmQ2E86L0RdNWVostwoZZ8 AsUGUAHw9xTRp3j5B29GJN9ERbWYpZNc4qKpJuIrnstuNbpoBOTZVB0DZCJYiR4M39+x GCNh9NdWJIUP+wQ2bmS6sEiN//Unm44dZ5lI5df6pEyyG1jEcdAkV+nhV9lPlX3QAh+N W3D/c40AyalxXcrPVinNedK9PIaOliJiHkkXpRihYBjAKChC5QZlU3h2FLrKBsJh4ans ZWskR+c9GDJ5fnaSLwPM1gyD1rgdQ+45CAdZlr9tiiiX3B5s3ZqOHKSPhQ/+lWGeq5iC eQhA==
X-Gm-Message-State: AOAM533jOdlL9J+yffFf4zJyjhWB+RrXKj1xwSr9JauIUW4vE8Qr3sUS HTyGU7elPPJXK4J7wG0ZHONJEczaHiKDgGhiYHg=
X-Google-Smtp-Source: ABdhPJzAMrx1rtlIu8N+EkQBYZdicHSCX0+dkJun6ss1LDL3jIrQ0iru+gWLkMG5+cNg1XJgqN/I+19VvYv4jifoj6w=
X-Received: by 2002:a92:1553:: with SMTP id v80mr11564745ilk.300.1600069837332; Mon, 14 Sep 2020 00:50:37 -0700 (PDT)
MIME-Version: 1.0
References: <200E7364-7635-4C21-9CF7-86C93EFB7E4F@comcast.com> <CABcZeBPuq86Fj0VYQ+1j8ZWo+4BT1bDJGfnRmi82oUc8Xns=PQ@mail.gmail.com>
In-Reply-To: <CABcZeBPuq86Fj0VYQ+1j8ZWo+4BT1bDJGfnRmi82oUc8Xns=PQ@mail.gmail.com>
From: tirumal reddy <kondtir@gmail.com>
Date: Mon, 14 Sep 2020 13:20:25 +0530
Message-ID: <CAFpG3gfhW0J2k4DSbkkunjrimQ_wKEvv6r6FSp7-9DOEuBOVTg@mail.gmail.com>
To: Eric Rescorla <ekr@rtfm.com>
Cc: "Deen, Glenn" <Glenn_Deen@comcast.com>, ADD Mailing list <add@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000004527fa05af414aee"
Archived-At: <https://mailarchive.ietf.org/arch/msg/add/jlG5MfRo4y4AVkLOcUlYDxmFSsM>
Subject: Re: [Add] Authentication Sub-topics for Tuesday Interim (homework for Tuesday's meeting)
X-BeenThere: add@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications Doing DNS <add.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/add>, <mailto:add-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/add/>
List-Post: <mailto:add@ietf.org>
List-Help: <mailto:add-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/add>, <mailto:add-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Sep 2020 07:50:40 -0000

On Mon, 14 Sep 2020 at 04:51, Eric Rescorla <ekr@rtfm.com> wrote:

> (1) What capabilities are we going to assume an attacker has in the local
> discovery model?
>

We can start with RFC 3552 and evaluate if a weaker threat model is
required.


> Do we have *any* candidate design which does anything useful in those
> circumstances? If so, what does that design do?
> (2) Do we have any secure way to tell clients which resolver the network
> wants them to use?
>

Yes, secure discovery is possible in certain deployments (e.g., Enterprise,
VPN) but not in networks with common passwords for WiFi
authentication/Opportunistic Wireless Encryption (susceptible to passive
and active attacks).



> (3) Assuming that we had a secure way to tell clients which resolver the
> network wanted them to use, what would we want to say there?
>

> Spoiler alert: I have opinions on the answers to these questions, but that
> seems like a topic for the interim.
>
> -Ekr
>
>
>
> On Fri, Sep 11, 2020 at 11:51 AM Deen, Glenn <Glenn_Deen@comcast.com>
> wrote:
>
>> Hi ADD,
>>
>>
>>
>> Authentication clearly has emerged as a topic important to the group.
>> It showed up during the ADD Interim on Sept 10th in both comments and in
>> jabber. Prior to that It has shown up in  drafts, list traffic and GitHub
>> issues.      Coming out of the Interim yesterday it was proposed as the
>> starting topic for the next interim on Tuesday Sept 15.
>>
>>
>>
>> To help focus and facilitate productive conversation the chairs would
>> like to ask for the group’s help in breaking down the topic of
>> authentication into sub-topics for Tuesday’s interim session.
>>
>>
>>
>> Here’s a small homework assignment for the next couple of days to help
>> set the Interim agenda:  We ask that ADD participants please take a few
>> minutes and post to this list thread authentication sub-topics you’d like
>> to cover.
>>
>>
>>
>> To get you thinking on the question,  consider that authentication has
>> come up in a variety of ADD discussions:
>>
>>
>>
>>       (1) Topic:  the question of can DHCP play a role in discovery which
>> has resulted in many saying “No” since it isn’t authenticated;
>>
>>       (2) Topic:  the question of authentication’s role in resolver
>> discovery and validation;
>>
>>       (3) Topic:  the question of authentication to enable identification
>> of resolvers that are associated or affiliated with one another or an
>> organization
>>
>>       ….
>>
>>
>>
>>
>>
>> This list is by no means complete and is meant to illustrate a few of the
>> places and contexts the topic of “Authentication” has popped up recently.
>>
>>
>>
>> Please share what authentication topic, scenario, role, need you believe
>> the ADD group should spend time discussing on the Tuesday agenda.
>>
>>
>>
>> Please limit discussion on this particular thread to only sharing what
>> authentication sub-topic aspect you’d like to see discussed and not expand
>> into a discussion of the sub-topics themselves.   Yes this all interesting
>> stuff, but the thread can quickly become overwhelming for readers to
>> follow.
>>
>>
>>
>> So limit, for now, responses to what you’d like to discuss – not the
>> actual technical discussion.
>>
>>
>>
>> Also, this may prompt some responders to feel like now it is a good time
>> to stray into policy discussions.   Please try to self-regulate and not go
>> there.    ADD is limited to technical mechanisms to do discovery and a
>> means to convey information about the discovered resolvers – and the
>> discussion needs to stay withing those boundaries.
>>
>>
>>
>> Regards
>>
>> Glenn Deen & David Lawrence – ADD Chairs
>> --
>> Add mailing list
>> Add@ietf.org
>> https://www.ietf.org/mailman/listinfo/add
>>
> --
> Add mailing list
> Add@ietf.org
> https://www.ietf.org/mailman/listinfo/add
>