On Mon, Jul 29, 2019 at 08:41:32PM +0200, Sebastian Kiesel wrote: > Hi, > > On Wed, Jul 17, 2019 at 03:52:19PM -0700, Benjamin Kaduk via Datatracker > wrote: > > Benjamin Kaduk has entered the following ballot position for > > draft-ietf-alto-xdom-disc-05: No Objection > > > > ---------------------------------------------------------------------- > > COMMENT: > > ---------------------------------------------------------------------- > > > > However, I do think that we need to clarify in Section 5.2.2 that this > > mechanism is compatible with the BCP 20 sub-allocation scheme only > > insamuch as you can add NAPTR records in the relevant locations -- the > > current procedures described in the text will not catch everything > > just on their own, IIUC. > > Thanks for your feedback and sorry that I have to ask, but > could you please be more specific about what you think is still missing?
Well, I was reading fairly fast so it's quite possible the confusion is/was on my end... I'm not 100% sure I know what "the relevant NAPTR resource records" are in "This ISP may populate the subdomain of in-addr.arpa. that corresponds to the whole /24 prefix with the relevant NAPTR resource records, even if BCP20-style delegations or no delegations at all are used"; would that be something like: 192/26.100.51.198.IN-ADDR.ARPA IN NAPTR <...> ? If there's anything in a different form than what's already shown in examples in section 3, it may be worth providing another example here, even though RFC 2317 will have the bulk of the relevant content. Thanks, Ben _______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
