n ANIMA/ACP via GRASP:
> > https://datatracker.ietf.org/doc/draft-eckert-anima-grasp-dnssd/
> > b) Use service discovery for ANIMA/ACP to autoconfigure its own core
> > services
> >
> > https://datatracker.ietf.org/doc/draft-eckert-anima-services-dns-auto
ACP to autoconfigure its own core services
https://datatracker.ietf.org/doc/draft-eckert-anima-services-dns-autoconfig/
Could I ask you to review and comment these two drafts ?
If the responses are not too averse, I will request a call for adoption.
Thanks
Toerless
Btw: I am happy to swap mutual review c
MA/ACP via GRASP:
https://datatracker.ietf.org/doc/draft-eckert-anima-grasp-dnssd/
b) Use service discovery for ANIMA/ACP to autoconfigure its own core services
https://datatracker.ietf.org/doc/draft-eckert-anima-services-dns-autoconfig/
Could I ask you to review and comment these two drafts
autoconfigure its own core services
https://datatracker.ietf.org/doc/draft-eckert-anima-services-dns-autoconfig/
Could I ask you to review and comment these two drafts ?
If the responses are not too averse, I will request a call for adoption.
Thanks
Toerless
Btw: I am happy to swap mutual
aft-eckert-anima-services-dns-autoconfig-00
this afternoon between other appointments.
I think that the Introduction needs to tell me a lot more about the problem
space.
The Day-0/Day-1 stuff, I sort of understood, but not really.
Is it relevant how the device got onto the ACP, if it wasn't BRS
I tried to read
https://datatracker.ietf.org/doc/html/draft-eckert-anima-services-dns-autoconfig-00
this afternoon between other appointments.
I think that the Introduction needs to tell me a lot more about the problem
space.
The Day-0/Day-1 stuff, I sort of understood, but not really.
Is it
