Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #26859

Closed (moved)
Open
Opened Jul 18, 2018 by dmr@dmr

Spec: improve contextual description of EXTEND->CREATE / CREATED->EXTENDED handling and payloads

catalyst noted in #tor-dev that 5.1.2 (EXTEND and EXTENDED) says nothing explicitly about an OR's (relays receiving an EXTEND or EXTEND2 cell) responsibility to send a corresponding CREATE/CREATE2 cell to the requested next node.

catalyst, asn, nickm, and I chatted a bit about it. I bought up that 5.3 mentions an OR's role of translating EXTEND -> CREATE and CREATED -> EXTENDED and suggested we might reference that section from 5.1 and 5.1.2.

It's probably enough to do that, but if some other change makes more sense (when actually putting together the wording), do that.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#26859