We have been discussing the applicability of this in the context of
advanced, dual stack premise networking.  From our perspective there is a
need for this particularly with regards to premises that have multiple,
routed subnets.


It seems to me that we need not reinvent the mechanisms for service
discovery/advertisement.

To comment on the question below, I believe we should be providing
guidance on this topic.  This will help to ensure that some minimum
functionality is specified.  This will still leave room for
differentiation, etc.

If the mechanism is provided then any service could conceivably be
discovered using the same.

Based on my thinking so far proxies could present resource challenges for
some types of devices, conversely extension may be slightly more
complicated.  More to come on proxy versus extension.

John 
-----Original Message-----
From: homenet issue tracker <[email protected]>
Date: Wed, 21 Mar 2012 23:42:35 +0000
To: <[email protected]>, Tim Chown
<[email protected]>
Cc: <[email protected]>
Subject: [homenet]  #8: Proxy or extend?
Resent-From: <[email protected]>
Resent-Date: Wed, 21 Mar 2012 16:42:42 -0700

>#8: Proxy or extend?
>
> Do we wish to state a preference for how protocols that currently work
> within a single subnet can be made to work within a multi-subnet homenet
> site?  Proxies could be defined at subnet boundaries (e.g. as per DHCPv6
> relays) or protocols could be extended to site scope (e.g. the recent
> xmDNS proposal). Or is this a per-protocol decision?
>
>-- 
>-------------------+---------------------------------------
> Reporter:  tjc@Š  |      Owner:  draft-ietf-homenet-arch@Š
>     Type:  task   |     Status:  new
> Priority:  major  |  Milestone:
>Component:  arch   |    Version:
> Severity:  -      |   Keywords:
>-------------------+---------------------------------------
>
>Ticket URL: <http://trac.tools.ietf.org/wg/homenet/trac/ticket/8>
>homenet <http://tools.ietf.org/homenet/>
>
>_______________________________________________
>homenet mailing list
>[email protected]
>https://www.ietf.org/mailman/listinfo/homenet

_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet

Reply via email to