FW: homenet session approved

Hi,

The requested BOF session has been approved. That's the good news. 

But there are caveats. I am in discussion with the other ADs and IAB
members to get these requirements stated just right, but I can tell
you the rough consensus from the IESG/IAB review of the BOF Request,
so you can begin to work on addressing the caveats:

IESG/IAB consensus is to approve scheduling of a BOF session, likely
to be turned into a WG session. However, that session is conditional.
If the WG proponents do not get the charter modified to reflect the
following tighter scope, the session will be cancelled, and the WG
will not be created.

1) The (conditional) working group is authorized to develop BCPs for
the features vendors should include in unmanaged home networking
devices.

2) Recommended home network architectures, protocol gap analysis, and
protocol modification recommendations can be done outside the WG, but
these are out of scope for the WG. These can instead be developed as
individual (or non-WG design team) drafts. 

3) no protocol development is approved for the WG. 

A summary of many IESG/IAB comments:
- Taking on the problem of home networks is welcome, but the charter
is too relaxed. The current charter seems to provide license to do
anything. We should not approve such an open-ended charter. I do not
know why this as broad as it is. We need a charter that is tightly
scoped and well understood; this was the focus of the last BOF, and
the WG. 
- It is unclear how home networks differ from other networks. The
charter does not provide enough information to make that
understandable. The charter needs to delimit the scope better by
mentioning the unmanaged nature of the devices, and other properties
of home networking devices that will serve to limit the scope.
- The chartered topics of consideration (currently the seven bullets)
need to be much more specific about the known problems that will be
addressed by BCPs.
- Specific concerns from other SDOs, such as Zigbee, can be handled
through liaisons, or maybe a directorate to talk to. The need for
cross-SDO collaboration does not by itself justify the creation of a
WG for this purpose. 
- The proposed work seems more oriented to INT than Transport.--
I recommend the chairs discuss this amongst themselves, think about
how you want to modify the charter to accommodate the caveats, and get
back to the INT/TSV ADs.

Let me know if these caveats are not clear, and if I can be of any
assistance.

David Harrington
Director, IETF Transport Area
 (preferred for ietf)

+1 603 828 1401 (cell)

David et al,

I must say I feel rather dejected by this message.> The requested BOF session has been approved. That's the good news. 
> 
> But there are caveats. I am in discussion with the other ADs and IAB
> members to get these requirements stated just right, but I can tell
> you the rough consensus from the IESG/IAB review of the BOF Request,
> so you can begin to work on addressing the caveats:
> 
> IESG/IAB consensus is to approve scheduling of a BOF session, likely
> to be turned into a WG session. However, that session is conditional.
> If the WG proponents do not get the charter modified to reflect the
> following tighter scope, the session will be cancelled, and the WG
> will not be created.
> 
> 1) The (conditional) working group is authorized to develop BCPs for
> the features vendors should include in unmanaged home networking
> devices.it appears the IESG/IAB consensus is back to creating "device profiles". we've been through a few rounds of discussion on the list and elsewhere on that already.
I'm not sure I see the value of doing that in the IETF. the work has already been done in BBF TR-124i2, CableLabs eRouter and HGI...

in addition we have the following IETF documents:
http://tools.ietf.org/html/rfc5625
NAT in behave
http://tools.ietf.org/html/rfc5684
http://tools.ietf.org/html/draft-ietf-v6ops-i...
http://tools.ietf.org/html/draft-ietf-v6ops-c...

I for one don't see what work is missing.> 2) Recommended home network architectures, protocol gap analysis, and
> protocol modification recommendations can be done outside the WG, but
> these are out of scope for the WG. These can instead be developed as
> individual (or non-WG design team) drafts.right, this is for me the interesting part. with this being outside the scope of the proposed working group and with no coupling with it, then this work could progress with or without homenet.

> 3) no protocol development is approved for the WG. 

indeed.

I would much rather have seen the IESG suggest how we could move forward with the proposed draft, instead of shackling the working group in this manner.

to me it doesn't seem to be a way forward homegate/homenet at this point. what would you propose we need to do, to make it more likely to succeed in the future? start working on the problems outlined in the latest draft? laying the ground work with architecture/framework documents...?

cheers,
Ole> 
> A summary of many IESG/IAB comments:
> - Taking on the problem of home networks is welcome, but the charter
> is too relaxed. The current charter seems to provide license to do
> anything. We should not approve such an open-ended charter. I do not
> know why this as broad as it is. We need a charter that is tightly
> scoped and well understood; this was the focus of the last BOF, and
> the WG. 
> - It is unclear how home networks differ from other networks. The
> charter does not provide enough information to make that
> understandable. The charter needs to delimit the scope better by
> mentioning the unmanaged nature of the devices, and other properties
> of home networking devices that will serve to limit the scope.
> - The chartered topics of consideration (currently the seven bullets)
> need to be much more specific about the known problems that will be
> addressed by BCPs.
> - Specific concerns from other SDOs, such as Zigbee, can be handled
> through liaisons, or maybe a directorate to talk to. The need for
> cross-SDO collaboration does not by itself justify the creation of a
> WG for this purpose. 
> - The proposed work seems more oriented to INT than Transport. 
> 
> --
> I recommend the chairs discuss this amongst themselves, think about
> how you want to modify the charter to accommodate the caveats, and get
> back to the INT/TSV ADs.
> 
> Let me know if these caveats are not clear, and if I can be of any
> assistance.
> 
> David Harrington
> Director, IETF Transport Area
>  (preferred for ietf)
> 
> +1 603 828 1401 (cell)
> 
> _______________________________________________
> homegate mailing list
> 
> https://www.ietf.org/mailman/listinfo/homegat...