BIND 10 #2534: support minor cases for quoted character strings

[BIND 10 Development]

#2534: support minor cases for quoted character strings
-------------------------------------+-------------------------------------
            Reporter:  jinmei        |                        Owner:  shane
                Type:  task          |                       Status:
            Priority:  medium        |  reviewing
           Component:  libdns++      |                    Milestone:
            Keywords:                |  bind10-1.2-release-freeze
           Sensitive:  0             |                   Resolution:
         Sub-Project:  DNS           |                 CVSS Scoring:
Estimated Difficulty:  4             |              Defect Severity:  N/A
         Total Hours:  0             |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------

Comment (by kean):

 Replying to [comment:16 muks]:

 > All 3 represent the same data. The example from the section in the SPF
 RFC I pointed to also demonstrates this equivalence. "v=spf1 .... first"
 "second string..." is the same as "v=spf1 .... firstsecond string...".
 They key difference in that example is that both strings are quoted, and
 the space between them is the separator. RFC4408 very explicitly says what
 to do in that case. However RFC1035 does not specify what to do with an
 unquoted string (i.e one that does not start with a quote) that contains a
 quote later in the string. What it says is fairly unambiguous to my
 reading: <character-string> is expressed in one or two ways: as a
 contiguous set of characters without interior spaces, or as a string
 beginning with a " and ending with a ". The input {{{Test-String"Test-
 String"}}} is very clearly a "contiguous set of characters without
 interior spaces".

 If the input was {{{Test-String "Test-String"}}}, ie with a space between
 them, then I totally agree that it would be a STRING followed by a
 QSTRING.

 > I'm assigning it to Shane for his thoughts so we can get to a resolution
 soon.
 Ok.

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