BIND 10 #2671: Clean up doc/design/cc-protocol.txt
BIND 10 Development
do-not-reply at isc.org
Tue Mar 5 08:54:01 UTC 2013
#2671: Clean up doc/design/cc-protocol.txt
-------------------------------------+-------------------------------------
Reporter: vorner | Owner: jelte
Type: task | Status:
Priority: medium | reviewing
Component: | Milestone:
documentation | Sprint-20130305
Keywords: | Resolution:
Sensitive: 0 | CVSS Scoring:
Sub-Project: Core | Defect Severity: N/A
Estimated Difficulty: 3 | Feature Depending on Ticket:
Total Hours: 0 | Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
Changes (by vorner):
* owner: vorner => jelte
Comment:
Hello
Replying to [comment:4 jelte]:
> The initial part about the 'instance' attribute in addressing might be a
tad too cynical :) It's probably more accurate to say we haven't found any
actual use for it (because we use name-by-convention, and more
importantly, the only time we send to specific instances is when we
reply), but so far it hasn't been a priority to actually remove it.
I made it sound more polite with regards to the header now.
Anyway, we don't use that even for that. We use the l-name for answering
and put it to the `to` header. We copy the instance from the original
message, so it is `*` as usual. I did see some ancient code somewhere
around configuration that did have an instance set, but that's an
exception. Looking at the semantics, I think it should rather be called
„subgroup“, not instance, since there can be multiple connections in the
same instance.
> One small improvement perhaps could be to explicitely specify the types
of the header fields.
Done
--
Ticket URL: <http://bind10.isc.org/ticket/2671#comment:5>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list