RE: Automatically connecting to stub networks...

[Vasilenko Eduard <[e-mail]>]

Hi Ted,
I believe that it is very big question should it be L2 or L3 solution for stub router?
Many ideas come to me on this subject immediately: L2 is not dependent on /64 problem, DNS is easy (including mDNS), etc.
But I do not know what is better – the matter is complex.
I have NOT found the discussion in your draft.
Eduard
From: ipv6 [mailto:[e-mail]] On Behalf Of Ted Lemon
Sent: 10 июля 2020 г. 9:25
To: 6MAN <[e-mail]>
Subject: Automatically connecting to stub networks...

I mentioned prior to IETF 107 that I wanted to start a conversation about this problem, but didn’t have time to write a draft.  I’ve written one, which I think describes my view of the problem pretty well; I’d like to know if what I’ve written here makes sense to others.  This is semi-related to the Homenet problem, but doesn’t try to do as much, which makes the problem a bit more tractable, and addresses at least one fairly important use case.

A new version of I-D, draft-lemon-stub-networks-ps-00.txt
has been successfully submitted by Ted Lemon and posted to the
IETF repository.

Name:                        draft-lemon-stub-networks-ps
Revision:       00
Title:             Self-configuring Stub Networks: Problem Statement
Document date:         2020-07-08
Group:                       Individual Submission
Pages:                        15
URL:            https://www.ietf.org/internet-drafts/draft-lemon-stub-networks-ps-00.txt
Status:         https://datatracker.ietf.org/doc/draft-lemon-stub-networks-ps/
Htmlized:       https://tools.ietf.org/html/draft-lemon-stub-networks-ps-00
Htmlized:       https://datatracker.ietf.org/doc/html/draft-lemon-stub-networks-ps


Abstract:
  IETF currently provides protocols for automatically connecting single
  hosts to existing network infrastructure.  This document describes a
  related problem: the problem of connecting a stub network (a
  collection of hosts behind a router) automatically to existing
  network infrastructure in the same manner.




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<http://tools.ietf.org>.

The IETF Secretariat