>
> It is my (possibly mistaken) understanding that the nature of an
> "endpoint" depends on the mode of operation. So why not use a more
> concrete definition?
The definition just gets more verbose with every iteration, the underlying
problematic is that it tries to unify different concepts that
On 13/07/2015 03:05, Steven Barth wrote:
...
>> => It is unclear to me how multiple instances of DNCP is run on a
>>link. Is that something that must be specified in the profile
>>document, and each profile must support multiple instances?
>>Given draft-stenberg-shsp, and the way it "h
On 13/07/2015 03:05, Steven Barth wrote:
> Hello Ole,
...
>> => Add a reference to Merkle trees?
> I'm not certain what would be a good source to quote here, maybe Merkle's
> paper from '87 or the ‘92 patent? At least there doesn't seem to be
> a really appropriate reference.
His PhD thesis seems
> "a locally configured communication endpoint of a DNCP node, such
> as a network socket. An endpoint may be bound to a set of
> predefined unicast Addresses representing remote DNCP nodes to
> individually connect to or to accept connections from whereby
> communicat
Hello Ole,
thanks again for your review and sorry for the delay.
Please find replies inline.
Cheers,
Steven & Markus
>
> Given that it is an "Abstract protocol" specification, that must be
> combined with a profile specification to be a fully implementable, it
> is somewhat difficult to predi
I have been selected as the Internet Directorate reviewer for this
draft. The purpose of the review is to provide assistance to the
Internet ADs.
Although these comments are primarily for the use of the Internet ADs,
it would be helpful if you could consider them along with any other
IETF Last Cal
