Yes, I’m good.
Thanks!!
Alvaro.
On 12/21/16, 1:13 PM, "Rob Austein" >
wrote:
I hope this addresses the issue.
___
sidr mailing list
sidr@ietf.org
https://www.ietf.org/mailman/listinfo/sidr
At Wed, 21 Dec 2016 12:20:54 +, Alvaro Retana (aretana) wrote:
...
> it still doesn?t tell me what the child should do. I don?t think
> you want to specify taking up one or the other, but at least include
> some text that says that the child can choose.
>
> In thinking about this I came up
Rob:
Hi!
You added some text about offer and referral:
A parent is unlikely to need to send both and
elements, but strictly speaking they are not mutually exclusive, so a
parent which really needs to express that it both offers repository
service to its child and is also willing to
Proposed -05, reflecting comments from AD review:
https://subvert-ietf.hactrn.net/rpki-oob-setup/draft-ietf-sidr-rpki-oob-setup-05.txt
https://subvert-ietf.hactrn.net/rpki-oob-setup/draft-ietf-sidr-rpki-oob-setup-05-from-04.diff.html
Absent objections, I will post to I-D repository,
On 12/20/16, 12:33 PM, "Rob Austein" wrote:
| At Tue, 20 Dec 2016 14:24:27 +, Alvaro Retana (aretana) wrote:
| | C1. Why isn?t an IETF namespace [RFC3688] used in the XML schema? I
| | would strongly suggest that you use one and request it in the IANA
| |
At Tue, 20 Dec 2016 14:24:27 +, Alvaro Retana (aretana) wrote:
>
> C1. Why isn?t an IETF namespace [RFC3688] used in the XML schema? I
> would strongly suggest that you use one and request it in the IANA
> Considerations Section. Unlike the publication protocol, this
> document specifies
Rob:
Hi! How are you?
I just finished reading this document. Thanks for the work!
I have some comments (below) that should be easy to address. I think the major
one is about the ordering of the XML attributes (C2); I’ll start the IETF Last
Call once (at least) that point is resolved.