Changeset 11095
- Timestamp:
- 05/20/08 23:49:23 (22 months ago)
- Files:
-
- 1 modified
-
dotorg/trunk/html/beps/bep_0007.rst (modified) (6 diffs)
Legend:
- Unmodified
- Added
- Removed
-
dotorg/trunk/html/beps/bep_0007.rst
r11031 r11095 8 8 Created: 31-Jan-2008 9 9 Post-History: 10 11 IPv6 tracker extension12 ======================13 10 14 11 This extension extends the tracker response to better support IPv6 peers as … … 26 23 .. _`RFC 2119`: http://tools.ietf.org/html/rfc2119 27 24 28 announce parameter29 ------------------ 25 Announce Parameter 26 ================== 30 27 31 28 The client MAY add an ``&ipv6=`` parameter to the HTTP GET request it sends … … 53 50 any ``&ipv6=`` parameter. 54 51 55 announce response56 ----------------- 52 Announce Response 53 ================= 57 54 58 In case the tracker does not support the ``compact`` response, no change is 59 necessary. Since the original ``peers`` response returns peer endpoints in 60 their expanded string form, IPv6 addresses can be passed back this way. 55 In case the tracker does not support the ``compact`` response as 56 described in BEP 23 `BEP-23`_, no change is necessary. Since the 57 original ``peers`` response returns peer endpoints in their expanded 58 string form, IPv6 addresses can be passed back this way. 61 59 62 60 In case a compact response is requested, the tracker MAY add another key … … 65 63 peers6 contains address-port pairs where the addresses are all IPv6. 66 64 67 examples 68 -------- 65 .. _`BEP-23`: http://www.bittorrent.org/beps/bep_0023.html 66 67 Examples 68 ======== 69 69 70 70 Example announce string with ``2001::53aa:64c:0:7f83:bc43:dec9`` as IPv6 … … 92 92 d8:intervali1800e5:peers6:iiiipp6:peers618:iiiiiiiiiiiiiiiippe 93 93 94 rationale95 --------- 94 Rationale 95 ========= 96 96 97 97 The naming of ``peers6`` is chosen not to collide with the current ``peers`` … … 101 101 102 102 Copyright 103 --------- 103 ========= 104 104 105 105 This document has been placed in the public domain.
