BIND 10 #2904: [kean] check violation of DO_NOT_USE_127.0.0.1:47807

[BIND 10 Development]

#2904: [kean] check violation of DO_NOT_USE_127.0.0.1:47807
-------------------------------------+-------------------------------------
            Reporter:  jinmei        |                        Owner:  kean
                Type:  defect        |                       Status:
            Priority:  medium        |  reviewing
           Component:  Unclassified  |                    Milestone:
            Keywords:                |  Sprint-20131015
           Sensitive:  0             |                   Resolution:
         Sub-Project:  DNS           |                 CVSS Scoring:
Estimated Difficulty:  2             |              Defect Severity:  N/A
         Total Hours:  0             |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
Changes (by muks):

 * owner:  muks => kean


Comment:

 Hi Kean

 I looked at your comments on Jabber this morning about this ticket.

 The port changes are fine. None of the builders seem affected by it.

 The change of all IPv6 configuration to IPv4 is also fine for the
 builders, but this appears as a regression. IIRC, ::1 was used in lettuce
 tests first to avoid a port problem on Jinmei's machine, but we have since
 then assumed that IPv6 is exercised by lettuce due to the presence of
 these tests.

 From your comments on Jabber, it seems you want to cleanly separate IPv6
 testing from functional testing of features. Such v6-specific testing
 would involve exercising the various components on IPv6 addresses (queries
 with b10-auth, xfrin and xfrout on IPv6 address, whether NOTIFY gets
 delivered on IPv6, etc.). This is a good idea.

 My concern is that if we switch everything to IPv4 loopback address
 without adding corresponding IPv6 tests, we will have a time when we don't
 do any system testing with IPv6 addresses.

 What I suggest is that you make the port changes alone first on a branch,
 get it reviewed and merge it to master. This will be quick as the port
 change is OK.

 Then, separate the IPv6 testing by adding new lettuce testcases (such as
 those listed above) for the various components. As part of that ticket,
 cleanup the lettuce IP address configurations.

-- 
Ticket URL: <http://bind10.isc.org/ticket/2904#comment:11>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development