BIP8: clarify deployment terms

Author: shaolinfry

bip-0149.mediawiki

@@ -22,6 +22,8 @@ Miners have been reluctant to signal the BIP9 segwit deployment despite a large
 
 ==Reference implementation==
 
+The reference implementation will refuse to run on Bitcoin mainnet before 7 November 2017, and can only be run on testnet and regtest until then.
+
 https://github.com/bitcoin/bitcoin/compare/master...shaolinfry:uasegwit-flagday
 
 ==Specification==
@@ -30,7 +32,9 @@ This deployment will set service bit (1<<5) as NODE_UAWITNESS.
 
 ==Deployment==
 
-This BIP will be deployed by BIP8 with the name "segwit" and using bit TBD.
+This BIP should only be deployed if BIP9-segwit fails to lock-in or activate before timeout on 15 November 2017. This BIP cannot be deployed before 15 November 2017.
+
+This BIP will be deployed by BIP8 with the name "segwit" and using bit 1.
 
 For Bitcoin mainnet, the BIP8 starttime will be midnight 16 November 2017 UTC (Epoch timestamp 1510790400) and BIP8 timeout will be 4 July 2018 UTC (Epoch timestamp 1530662400).
 
@@ -40,11 +44,11 @@ For Bitcoin testnet, segwit is already activated so no deployment is specified.
 
 This deployment reuses the GBT deployment name "segwit" to maintain compatibility with existing mining software.
 
-==Rationale==
+This deployment is incompatible with the BIP9-segwit deployment and should not be run concurrently with it.
 
-This BIP can be deployed well in advance of the BIP8 '''starttime''' so that the '''timeout''' will be sufficiently far in the future to allow Bitcoin users to upgrade in preparation.
+==Rationale==
 
-The '''starttime''' of this BIP is after the BIP9 "segwit" timeout to remove compatibility issues with old nodes.
+The '''starttime''' of this BIP is after the BIP9-segwit timeout to remove compatibility issues with old nodes.
 
 ==References==