The HNA MUST produce CDS/CDSKEY.
But, we have little control over whether or not the *parent zone* actually
uses CDS/CDSKEY.
We RECOMMEND that that they do (and maybe this RFC could be used as a
hammer), but it's outside of the control of the Outsourced Infrastructure
operator.
--
Michael Richa
On Fri, Nov 25, 2022 at 3:19 PM Daniel Migault wrote:
>
>
>>
>>Though the HNA may also later directly update the values of the DS
>>via the Control Channel, it is RECOMMENDED to use other mechanisms
>>such as CDS and CDNSKEY [RFC7344] for transparent updates during key
>>roll over
v6ops wrote:
> Michael Richardson wrote on 02/12/2022 02:56:
>> In re-editing I found that the section 7.1 is a bit vague about where
>> the Notifies go. Ray Hunter please comment.
>>
>>
https://www.ietf.org/archive/id/draft-ietf-homenet-front-end-naming-delegation-22.html#n
Hi Michael.
Michael Richardson wrote on 02/12/2022 02:56:
In re-editing I found that the section 7.1 is a bit vague about where the
Notifies go. Ray Hunter please comment.
https://www.ietf.org/archive/id/draft-ietf-homenet-front-end-naming-delegation-22.html#name-securing-the-synchronizatio
S
On Fri, Dec 2, 2022 at 9:50 AM Michael Richardson
wrote:
>
> Daniel Migault wrote:
> > In my opinion the Synchronization Channel is initiated by the DM and
> > follows AXFR over TLS (9103). To my understanding NOTIFY, SOA
> exchange
> > may be protected by TLS or not. Of course if th
Daniel Migault wrote:
> In my opinion the Synchronization Channel is initiated by the DM and
> follows AXFR over TLS (9103). To my understanding NOTIFY, SOA exchange
> may be protected by TLS or not. Of course if the TLS session has not
> been established by the DM the NOTIFY cann
Hi Michael,
Just sharing my thoughts,
Yours,
Daniel
On Thu, Dec 1, 2022 at 8:56 PM Michael Richardson wrote:
> In re-editing I found that the section 7.1 is a bit vague about where the
> Notifies go. Ray Hunter please comment.
>
>
> https://www.ietf.org/archive/id/draft-ietf-homenet-front-end-
In re-editing I found that the section 7.1 is a bit vague about where the
Notifies go. Ray Hunter please comment.
https://www.ietf.org/archive/id/draft-ietf-homenet-front-end-naming-delegation-22.html#name-securing-the-synchronizatio
Since the Synchronization Channel is from the DM->HNA, it can'
Hi Paul,
As mentioned offline, I am rebooting the conversation and addressing the
DISCUSS and comments. Please let me know if there is anything that needs to
be clarified or if additional information is needed. I tried to remain
quite high level in my responses in an effort to address high level
c
On Wed, Nov 23, 2022 at 9:12 AM Paul Wouters wrote:
> On Nov 22, 2022, at 16:15, Daniel Migault wrote:
> >
> >
> > Hi Paul,
> >
> > I am doing the follow-up and would like to check if there are any
> specific questions regarding the current version of the document.
>
> During IETF-115 I talked
On Nov 22, 2022, at 16:15, Daniel Migault wrote:
>
>
> Hi Paul,
>
> I am doing the follow-up and would like to check if there are any specific
> questions regarding the current version of the document.
During IETF-115 I talked to Michael. It helped confirm the parts that I thought
were un
Hi Paul,
I am doing the follow-up and would like to check if there are any specific
questions regarding the current version of the document.
Yours,
Daniel
On Mon, Oct 31, 2022 at 10:34 PM Daniel Migault wrote:
> Ray implemented the front end naming architecture but I am unaware if
> there is a
Hi,
I have an implementation of this specification.
It's not open source today.
But if it were to be published I'd be willing to discuss publishing the
code as open source.
(I am self-employed so there's no IPR issues in that).
regards,
Juliusz Chroboczek wrote on 01/11/2022 12:22:
Juliusz
On Tue, Nov 1, 2022 at 6:11 AM Juliusz Chroboczek wrote:
> Removing the IESG from CC.
>
> > I propose you start mentioning what you believe are unspecified gaps
> > that could lead to interoperability issues.
>
> With all due respect, Daniel, I'm a little surprised by this development.
> In this
> Juliusz, please go read RFC2026. You are completely out of order.
> Proposed standards do not need *ANY* interoperable implementations.
Usually, neither implementation nor operational experience is
required for the designation of a specification as a Proposed
Standard. However, such ex
Juliusz Chroboczek wrote:
> In this WG, we did spend a lot of effort ensuring that all of our
> specifications have at least two independent implementations.
Juliusz, please go read RFC2026. You are completely out of order.
Proposed standards do not need *ANY* interoperable implementatio
Removing the IESG from CC.
> I propose you start mentioning what you believe are unspecified gaps
> that could lead to interoperability issues.
With all due respect, Daniel, I'm a little surprised by this development.
In this WG, we did spend a lot of effort ensuring that all of our
specification
Daniel Migault wrote:
> will be able to address those or clarify them. I propose you start
> mentioning what you believe are unspecified gaps that could lead to
> INTEROPERABILITY ISSUES.
I emphasize this point.
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consultin
Ray implemented the front end naming architecture but I am unaware if there
is any link to an open source implementation.
I am unable to figure out what you believe is out of scope of the document
(or not), as gaps you believe are under specified. If stated explicitly we
will be able to address t
On Oct 31, 2022, at 09:39, Daniel Migault wrote:
>
>
> Hi Paul,
>
> This is just a follow-up regarding the remaining concerns that need to be
> solved. Does Michael's response address your questions, if not please let us
> know what remains unclear as well as what other clarification is nee
Hi Paul,
This is just a follow-up regarding the remaining concerns that need to be
solved. Does Michael's response address your questions, if not please
let us know what remains unclear as well as what other clarification is
needed.
Yours,
Daniel
On Tue, Oct 25, 2022 at 8:08 AM Michael Richardso
Paul Wouters wrote:
> These two sentences I think show the core of my lack of understanding.
> Let's say I want to put my sauna on my public home net so I can access it
> remotely and turn it on before I get home?
> Is this envisioned as a goal of the homenet architecture?
You s
On Sun, Oct 23, 2022 at 10:30 PM Daniel Migault wrote:
> Thanks Paul for the review,
>
> Most of the DISCUSS was composed of questions we answered all of them, and
> updated the text when necessary. You can see the change below:
>
> https://github.com/ietf-homenet-wg/ietf-homenet-hna/commit/27233
Thanks Paul for the review,
Most of the DISCUSS was composed of questions we answered all of them, and
updated the text when necessary. You can see the change below:
https://github.com/ietf-homenet-wg/ietf-homenet-hna/commit/27233e962f66ad72db91dac7ec7b65b7cd3b00f4
We clarified the TTL and the us
Paul Wouters has entered the following ballot position for
draft-ietf-homenet-front-end-naming-delegation-18: Discuss
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Pl
25 matches
Mail list logo
