Loading ...
Sorry, an error occurred while loading the content.

Re: minor editorial issues in draft-ietf-http-v11-spec-rev-06.txt

Expand Messages
  • Roy T. Fielding
    ... Ummm, while you are at it, you might also want to fix ================ 4.1 Message Types: Change generic-message = start-line *message-header CRLF [
    Message 1 of 7 , Mar 1, 1999
    View Source
    • 0 Attachment
      >Section 3.6.1 "Chunked Transfer Coding"
      >Change
      > trailer = *entity-header
      >to
      > trailer = *(entity-header CRLF)


      Ummm, while you are at it, you might also want to fix

      ================
      4.1 Message Types:
      Change
      generic-message = start-line
      *message-header
      CRLF
      [ message-body ]
      to
      generic-message = start-line
      *(message-header CRLF)
      CRLF
      [ message-body ]
      ================
      4.2 Message Headers:
      Change
      message-header = field-name ":" [ field-value ] CRLF
      to
      message-header = field-name ":" [ field-value ]
      ================
      5 Request
      Change
      Request = Request-Line ; Section 5.1
      *( general-header ; Section 4.5
      | request-header ; Section 5.3
      | entity-header ) ; Section 7.1
      CRLF
      [ message-body ] ; Section 4.3
      to
      Request = Request-Line ; Section 5.1
      *(( general-header ; Section 4.5
      | request-header ; Section 5.3
      | entity-header ) CRLF) ; Section 7.1
      CRLF
      [ message-body ] ; Section 4.3
      ================
      6 Response
      Change
      Response = Status-Line ; Section 6.1
      *( general-header ; Section 4.5
      | response-header ; Section 6.2
      | entity-header ) ; Section 7.1
      CRLF
      [ message-body ] ; Section 7.2
      to
      Response = Status-Line ; Section 6.1
      *(( general-header ; Section 4.5
      | response-header ; Section 6.2
      | entity-header ) CRLF) ; Section 7.1
      CRLF
      [ message-body ] ; Section 7.2
      ================

      Note that these are all the same error, and it's been in the spec
      since the very first draft (November 28, 1994). *sigh*
      I'll let you decide whether or not to forward this to the RFC editor.

      ....Roy
    • Larry Masinter
      I see that we ve been inconsistent about whether -header BNF non-terminals include or do not include CRLF. If there s no objection, I will forward these
      Message 2 of 7 , Mar 1, 1999
      View Source
      • 0 Attachment
        I see that we've been inconsistent about whether -header BNF
        non-terminals include or do not include CRLF.

        If there's no objection, I will forward these requests to
        the RFC editor as well; I imagine that Keith will need to
        ask for IESG approval.

        I hope there aren't a lot more like these, or we might be
        forced to reballot.

        Larry
        --
        http://www.parc.xerox.com/masinter

        > -----Original Message-----
        > From: Roy T. Fielding [mailto:fielding@...]
        > Sent: Monday, March 01, 1999 5:22 AM
        > To: Larry Masinter
        > Cc: Keith Moore; http-wg@...
        > Subject: Re: minor editorial issues in
        > draft-ietf-http-v11-spec-rev-06.txt
        >
        >
        > >Section 3.6.1 "Chunked Transfer Coding"
        > >Change
        > > trailer = *entity-header
        > >to
        > > trailer = *(entity-header CRLF)
        >
        >
        > Ummm, while you are at it, you might also want to fix
        >
        > ================
        > 4.1 Message Types:
        > Change
        > generic-message = start-line
        > *message-header
        > CRLF
        > [ message-body ]
        > to
        > generic-message = start-line
        > *(message-header CRLF)
        > CRLF
        > [ message-body ]
        > ================
        > 4.2 Message Headers:
        > Change
        > message-header = field-name ":" [ field-value ] CRLF
        > to
        > message-header = field-name ":" [ field-value ]
        > ================
        > 5 Request
        > Change
        > Request = Request-Line ; Section 5.1
        > *( general-header ; Section 4.5
        > | request-header ; Section 5.3
        > | entity-header ) ; Section 7.1
        > CRLF
        > [ message-body ] ; Section 4.3
        > to
        > Request = Request-Line ; Section 5.1
        > *(( general-header ; Section 4.5
        > | request-header ; Section 5.3
        > | entity-header ) CRLF) ; Section 7.1
        > CRLF
        > [ message-body ] ; Section 4.3
        > ================
        > 6 Response
        > Change
        > Response = Status-Line ; Section 6.1
        > *( general-header ; Section 4.5
        > | response-header ; Section 6.2
        > | entity-header ) ; Section 7.1
        > CRLF
        > [ message-body ] ; Section 7.2
        > to
        > Response = Status-Line ; Section 6.1
        > *(( general-header ; Section 4.5
        > | response-header ; Section 6.2
        > | entity-header ) CRLF) ; Section 7.1
        > CRLF
        > [ message-body ] ; Section 7.2
        > ================
        >
        > Note that these are all the same error, and it's been in the spec
        > since the very first draft (November 28, 1994). *sigh*
        > I'll let you decide whether or not to forward this to the RFC editor.
        >
        > ....Roy
        >
      • Kalvinder Singh
        ... Has this one been picked up... Section 3.6 Change transfer-coding = chunked | transfer-extension to transfer-encoding = chunked |
        Message 3 of 7 , Mar 1, 1999
        View Source
        • 0 Attachment
          "Roy T. Fielding" wrote:
          >
          > >Section 3.6.1 "Chunked Transfer Coding"
          > >Change
          > > trailer = *entity-header
          > >to
          > > trailer = *(entity-header CRLF)
          >


          Has this one been picked up...

          Section 3.6

          Change
          transfer-coding = "chunked" | transfer-extension
          to
          transfer-encoding = "chunked" | transfer-extension


          Found in draft-ietf-http-v11-spec-rev-06.

          Cheers,
          Kal.

          --
          . Kalvinder Singh singh@...
          _-_|\ Software Engineering Australia
          / \<-- Compaq
          \_.-._/ Research Park, Bond University Phone: +61 7 5575 0106
          v Gold Coast, Qld, 4229, Australia Fax: +61 7 5575 0100
        • Roy T. Fielding
          ... No, that is not an error. tansfer-coding and transfer-encoding are two different BNF rules. ....Roy
          Message 4 of 7 , Mar 1, 1999
          View Source
          • 0 Attachment
            >Has this one been picked up...
            >
            >Section 3.6
            >
            >Change
            > transfer-coding = "chunked" | transfer-extension
            >to
            > transfer-encoding = "chunked" | transfer-extension

            No, that is not an error. tansfer-coding and transfer-encoding are two
            different BNF rules.

            ....Roy
          • Kalvinder Singh
            ... Some Questions then... Question 1) Why isn t there a header definition of transfer-coding in Section 14? Question 2) In Section 14.41 Transfer-Encoding
            Message 5 of 7 , Mar 1, 1999
            View Source
            • 0 Attachment
              "Roy T. Fielding" wrote:
              >
              > >Has this one been picked up...
              > >
              > >Section 3.6
              > >
              > >Change
              > > transfer-coding = "chunked" | transfer-extension
              > >to
              > > transfer-encoding = "chunked" | transfer-extension
              >
              > No, that is not an error. tansfer-coding and transfer-encoding are two
              > different BNF rules.
              >

              Some Questions then...

              Question 1)

              Why isn't there a header definition of "transfer-coding" in Section 14?


              Question 2)

              In "Section 14.41 Transfer-Encoding" the following is stated...

              Transfer-codings are defined in section 3.6. An example is:
              Transfer-Encoding: chunked

              Is this an error???


              Cheers,
              Kal.

              --
              . Kalvinder Singh singh@...
              _-_|\ Software Engineering Australia
              / \<-- Compaq
              \_.-._/ Research Park, Bond University Phone: +61 7 5575 0106
              v Gold Coast, Qld, 4229, Australia Fax: +61 7 5575 0100
            • Kalvinder Singh
              Sorry about the bandwidth...:( I just answered my own questions, or I should say that you answered it in your first reply...;) Once again I am sorry. Cheers,
              Message 6 of 7 , Mar 1, 1999
              View Source
              • 0 Attachment
                Sorry about the bandwidth...:(

                I just answered my own questions, or I should say that you answered it
                in your first reply...;)

                Once again I am sorry.

                Cheers,
                Kal.

                Kalvinder Singh wrote:
                >
                > "Roy T. Fielding" wrote:
                > >
                > > >Has this one been picked up...
                > > >
                > > >Section 3.6
                > > >
                > > >Change
                > > > transfer-coding = "chunked" | transfer-extension
                > > >to
                > > > transfer-encoding = "chunked" | transfer-extension
                > >
                > > No, that is not an error. tansfer-coding and transfer-encoding are two
                > > different BNF rules.
                > >
                >
                > Some Questions then...
                >
                > Question 1)
                >
                > Why isn't there a header definition of "transfer-coding" in Section 14?
                >
                > Question 2)
                >
                > In "Section 14.41 Transfer-Encoding" the following is stated...
                >
                > Transfer-codings are defined in section 3.6. An example is:
                > Transfer-Encoding: chunked
                >
                > Is this an error???
                >
                > Cheers,
                > Kal.
                >
                > --
                > . Kalvinder Singh singh@...
                > _-_|\ Software Engineering Australia
                > / \<-- Compaq
                > \_.-._/ Research Park, Bond University Phone: +61 7 5575 0106
                > v Gold Coast, Qld, 4229, Australia Fax: +61 7 5575 0100

                --
                . Kalvinder Singh singh@...
                _-_|\ Software Engineering Australia
                / \<-- Compaq
                \_.-._/ Research Park, Bond University Phone: +61 7 5575 0106
                v Gold Coast, Qld, 4229, Australia Fax: +61 7 5575 0100
              Your message has been successfully submitted and would be delivered to recipients shortly.