Re: [homenet] WG Last Call for draft-ietf-homenet-dncp-03

2015-05-28 Thread Markus Stenberg
> On 28.5.2015, at 23.45, Juliusz Chroboczek > wrote: > > >> Section 5.2 explicitly says how to reach to each TLV (and no semantics >> about this, IIRC). > >> Section 5.3 states what Node Endpoint TLV means (=I want to be your >> neighbor), section 5 (start) says that that TLV is used for for

Re: [homenet] WG Last Call for draft-ietf-homenet-dncp-03

2015-05-28 Thread Juliusz Chroboczek
> Section 5.2 explicitly says how to reach to each TLV (and no semantics > about this, IIRC). > Section 5.3 states what Node Endpoint TLV means (=I want to be your > neighbor), section 5 (start) says that that TLV is used for forming > bidirectional peer relationships.. > How would you make it m

Re: [homenet] WG Last Call for draft-ietf-homenet-dncp-03

2015-05-28 Thread Markus Stenberg
On 28.5.2015, at 19.20, Dave Taht wrote: (3) it is impossible to act as a dumb DNCP forwarder without publishing a Node-State TLV and a full set of Neighbor sub-TLVs. >>> This is not true. Given basic bridging of ‘remember one guy on end of >>> each link’, you can do essentially bridging

Re: [homenet] WG Last Call for draft-ietf-homenet-dncp-03

2015-05-28 Thread Markus Stenberg
On 28.5.2015, at 18.38, Juliusz Chroboczek wrote: >>> (1) it is impossible to reliably snoop the protocol without contributing >>> a Node-State TLV and a full set of Neighbor sub-TLVs; >> This is not true, at least assuming the profile specifies even partially >> multicast-using profile. In pure

Re: [homenet] WG Last Call for draft-ietf-homenet-dncp-03

2015-05-28 Thread Dave Taht
>>> (3) it is impossible to act as a dumb DNCP forwarder without publishing >>> a Node-State TLV and a full set of Neighbor sub-TLVs. > >> This is not true. Given basic bridging of ‘remember one guy on end of >> each link’, you can do essentially bridging. so my use case (wanting routers without a

Re: [homenet] WG Last Call for draft-ietf-homenet-dncp-03

2015-05-28 Thread Juliusz Chroboczek
>> (1) it is impossible to reliably snoop the protocol without contributing >> a Node-State TLV and a full set of Neighbor sub-TLVs; > This is not true, at least assuming the profile specifies even partially > multicast-using profile. In pure unicast setup, you have to poll, > I guess. (HNCP isn’t

Re: [homenet] WG Last Call for draft-ietf-homenet-dncp-03

2015-05-28 Thread Markus Stenberg
On 28.5.2015, at 16.11, Juliusz Chroboczek wrote: > >> Thank you for the recent reviews and update of draft-ietf-homenet-dncp. >> Please take the next 3 weeks to make your final reviews. > > I strongly support this work. We have recently set up an HNCP experiment > here in Paris (together with

Re: [homenet] WG Last Call for draft-ietf-homenet-dncp-03

2015-05-28 Thread Juliusz Chroboczek
> Thank you for the recent reviews and update of draft-ietf-homenet-dncp. > Please take the next 3 weeks to make your final reviews. I strongly support this work. We have recently set up an HNCP experiment here in Paris (together with Thomas Denecker), and in the superficial testing we did, it wo

Re: [homenet] WG Last Call for draft-ietf-homenet-dncp-03

2015-05-26 Thread Brian E Carpenter
Hi, This is really just an FYI for the WG, not a direct comment on the draft. The latest posted draft of the proposed Anima signalling protocol is draft-carpenter-anima-gdn-protocol-03. It's by no means a WG draft and big changes may be coming. However, the present draft attempts to use a TLV for

[homenet] WG Last Call for draft-ietf-homenet-dncp-03

2015-05-06 Thread Mark Townsley
Dear WG, Thank you for the recent reviews and update of draft-ietf-homenet-dncp. Please take the next 3 weeks to make your final reviews. WG Last Call will officially end on May 28. Thank you, - Mark and Ray On Thu, Mar 5, 2015 at 3:25 PM, Ray Bellis wrote: > > Please provide further reviews