Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] Fwd: [homenet] Last Call: <draft-ietf-homenet-arch-10.txt> (Home Networking Architecture for IPv6) to Informational RFC
Date: Sat, 3 Aug 2013 10:13:00 -0700	[thread overview]
Message-ID: <CAA93jw7S=HE9jZhH02=zcnEOPtDoPrEHQEO24PqYgP0Aqf3ysw@mail.gmail.com> (raw)
In-Reply-To: <20130803165901.18120.73565.idtracker@ietfa.amsl.com>

In case anyone wants to review this... I haven't had a chance to
review the full document in several releases, there was certainly some
controversy over some sections in the last go-round that I don't know
were resolved adaquately.

please send your reviews to the appropriate list, not this one... if
you have questions poke at the homenet list.

---------- Forwarded message ----------
From: The IESG <iesg-secretary@ietf.org>
Date: Sat, Aug 3, 2013 at 9:59 AM
Subject: [homenet] Last Call: <draft-ietf-homenet-arch-10.txt> (Home
Networking	Architecture for IPv6) to Informational RFC
To: IETF-Announce <ietf-announce@ietf.org>
Cc: homenet@ietf.org



The IESG has received a request from the Home Networking WG (homenet) to
consider the following document:
- 'Home Networking Architecture for IPv6'
  <draft-ietf-homenet-arch-10.txt> as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2013-08-17. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   This text describes evolving networking technology within
   increasingly large residential home networks.  The goal of this
   document is to define a general architecture for IPv6-based home
   networking, describing the associated principles, considerations and
   requirements.  The text briefly highlights specific implications of
   the introduction of IPv6 for home networking, discusses the elements
   of the architecture, and suggests how standard IPv6 mechanisms and
   addressing can be employed in home networking.  The architecture
   describes the need for specific protocol extensions for certain
   additional functionality.  It is assumed that the IPv6 home network
   is not actively managed, and runs as an IPv6-only or dual-stack
   network.  There are no recommendations in this text for the IPv4 part
   of the network.




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-homenet-arch/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-homenet-arch/ballot/


No IPR declarations have been submitted directly on this I-D.


_______________________________________________
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet


-- 
Dave Täht

Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html

           reply	other threads:[~2013-08-03 17:13 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20130803165901.18120.73565.idtracker@ietfa.amsl.com>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAA93jw7S=HE9jZhH02=zcnEOPtDoPrEHQEO24PqYgP0Aqf3ysw@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox